Wazeopedia wazeopedia_philippines https://www.waze.com/wiki/Philippines/Main_Page MediaWiki 1.36.4 first-letter Media Special Talk User User talk Wazeopedia Wazeopedia talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Form Form talk Widget Widget talk Campaign Campaign talk Translations Translations talk Gadget Gadget talk Gadget definition Gadget definition talk 0 1 4551 1 2009-02-18T10:28:20Z MediaWiki default 0 wikitext text/x-wiki <big>'''MediaWiki has been successfully installed.'''</big> Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] bd962048d95fbb6b6b514885867811db20a5476b 10045 2013-07-07T08:43:19Z Kazmuth 35 Created page with "<big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development)" wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) 3bcd607d75f7c98fab72d7d4f41758e42d40662e 10046 10045 2013-07-09T03:51:12Z Kazmuth 35 wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users] [[Category:Philippines]] 5fa4f849426ce2ac3e4478629bd35c854d0b60f0 10047 10046 2013-07-21T08:45:23Z Kazmuth 35 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] 175a19b7438ee6e5411b25682ca8a09e2c57d541 10048 10047 2013-07-21T10:51:19Z Kazmuth 35 wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] 6c13641b921f40283c82ca1da2f8555b92b534fa 10049 10048 2013-07-21T10:53:49Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== '''Pinoy wazers''', [[Editing Resources for the Philippines]] is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] c2b6286941a63efb3e39ec52a9ba630f0a2cb23b 10050 10049 2013-07-21T10:59:35Z Kazmuth 35 wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) Welcome Pinoy Wazer, if you are reading this then you want to edit the map because you want to add a new road or have found a map issue. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== '''Pinoy wazers''', [[Editing Resources for the Philippines]] is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] b674a01c73dff5e8543367740e2e2ff370542995 10051 10050 2013-07-22T02:48:01Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) Welcome Pinoy Wazer, if you are reading this then you want to edit the map because you want to add a new road or have found a map issue. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Editing Resources for the Philippines]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - After reading the editing manual as well as the Philippine Map Editing Guide, you can apply to be an Area Manager in the Philippines using this form. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] c20c1a6f7d23f47b76c073dd8eed2a313c7c499f 10052 10051 2013-07-22T02:56:52Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) Welcome Pinoy Wazer, if you are reading this then you want to edit the map because you want to add a new road or have found a map issue. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Editing Resources for the Philippines]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - After reading the editing manual as well as the Philippine Map Editing Guide, you can apply to be an Area Manager in the Philippines using this form. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] 3da9a89d340c631c44b912b1990707a7e76afafd 10053 10052 2013-07-22T03:59:00Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) Welcome Pinoy Wazer, if you are reading this then you want to edit the map because you want to add a new road or have found a map issue. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Editing Resources for the Philippines]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - After reading the editing manual as well as the Philippine Map Editing Guide, you can apply to be an Area Manager in the Philippines using this form. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] fa014cb1acdf68a610bd0bf20bb5ff18ba19e62d 10054 10053 2013-07-23T01:25:03Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) Welcome Pinoy Wazer, if you are reading this then you want to edit the map because you want to add a new road or have found a map issue. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Editing Resources for the Philippines]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - After reading the editing manual as well as the Philippine Map Editing Guide, you can apply to be an Area Manager in the Philippines using this form. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] 6b245528e14e644c0a36bf70dd59526c88efba18 10055 10054 2013-10-18T00:45:20Z Kazmuth 35 wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map because you want to add a new road or have found a map issue. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Editing Resources for the Philippines]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - After reading the editing manual as well as the Philippine Map Editing Guide, you can apply to be an Area Manager in the Philippines using this form. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] c8f216a73be72e142acfb0c996d6397ed9bf8dba 10056 10055 2013-10-18T00:46:05Z Kazmuth 35 wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Editing Resources for the Philippines]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - After reading the editing manual as well as the Philippine Map Editing Guide, you can apply to be an Area Manager in the Philippines using this form. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] daf2e1963f09d8d46bf793c9bc3fd91e38ecf9cf 10057 10056 2013-10-18T00:46:34Z Kazmuth 35 wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Editing Resources for the Philippines]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - After reading the editing manual as well as the Philippine Map Editing Guide, you can apply to be an Area Manager in the Philippines using this form. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] a8a9cb3cae25748922ef23006b186d7fc4c950c0 0 2 10074 2013-07-21T10:50:47Z Kazmuth 35 Created page with "'''Pinoy wazers''', this is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests ..." wikitext text/x-wiki '''Pinoy wazers''', this is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled, you can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads&nbsp;within a commercial or private parking lots, not used for routing * Private Road – driveable roads&nbsp;within gated communities, subdivisions, villages, or compounds. Not used for routing * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the CITY of your edits. Unlike STREET names which reflects edits (or corrections) quicker and appears on the next update, CITY names unfortunately embeds much longer&nbsp;on the CITY tiles in the servers. So misspelled CITY names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the OFFICIAL (but shortest possible) NAME of the jurisdiction being edited. Also, if you are UNSURE of the POLITICAL BOUNDARIES of the "CITY" you are editing, leave it at that for the moment. let's leave it to the more experienced & knowledgeable editors to sort this mater out. Another matter of&nbsp;CITY&nbsp;labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are&nbsp;QUEZON, CEBU, DAVAO, CAVITE, etc as these cities have a&nbsp;provincial&nbsp;counterpart.&nbsp; This will distinguish&nbsp;Quezon City&nbsp;with the&nbsp;province of Quezon,&nbsp;Cebu City&nbsp;with the&nbsp;province of Cebu, so on & so forth. All other cities (& municipalities) will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P)&nbsp;for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9.&nbsp;'''Do not split roads unless'''&nbsp;they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road&nbsp;'''should'''&nbsp;be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road&nbsp;'''should not'''&nbsp;be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes - do not create dedicated turn lanes'''&nbsp;unless you can see distinct GPS tracks when you zoom in at 100m level. Or if there is an automatic update request from Waze that suggests you add the turn lane. 10. When you are confident on an area you have mapped,'''&nbsp;lock the roads'''&nbsp;to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed &nbsp;and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits.'''&nbsp;Tollways and Major highways are to be locked to level 4'''&nbsp;because these will rarely change so will require little to no editing.&nbsp;'''Minor and Primary streets are to be locked to level 3'''&nbsp;so they can be managed by their respective Area Managers. Other streets are to be locket to level 3 at the discretion of the Area Managers responsible for them. 11.'''&nbsp;Adding Landmarks and Gas Stations'''; Waze doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark and Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile.'''&nbsp;''' 12.&nbsp;'''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than made complex, therefore&nbsp;simplicity&nbsp;should be a key goal in&nbsp;design&nbsp;and unnecessary complexity should be avoided. 9652c1e11623114169f6b41f492f133a04387f5e 10075 10074 2013-07-21T10:53:37Z Kazmuth 35 wikitext text/x-wiki 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled, you can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads&nbsp;within a commercial or private parking lots, not used for routing * Private Road – driveable roads&nbsp;within gated communities, subdivisions, villages, or compounds. Not used for routing * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the CITY of your edits. Unlike STREET names which reflects edits (or corrections) quicker and appears on the next update, CITY names unfortunately embeds much longer&nbsp;on the CITY tiles in the servers. So misspelled CITY names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the OFFICIAL (but shortest possible) NAME of the jurisdiction being edited. Also, if you are UNSURE of the POLITICAL BOUNDARIES of the "CITY" you are editing, leave it at that for the moment. let's leave it to the more experienced & knowledgeable editors to sort this mater out. Another matter of&nbsp;CITY&nbsp;labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are&nbsp;QUEZON, CEBU, DAVAO, CAVITE, etc as these cities have a&nbsp;provincial&nbsp;counterpart.&nbsp; This will distinguish&nbsp;Quezon City&nbsp;with the&nbsp;province of Quezon,&nbsp;Cebu City&nbsp;with the&nbsp;province of Cebu, so on & so forth. All other cities (& municipalities) will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P)&nbsp;for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9.&nbsp;'''Do not split roads unless'''&nbsp;they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road&nbsp;'''should'''&nbsp;be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road&nbsp;'''should not'''&nbsp;be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes - do not create dedicated turn lanes'''&nbsp;unless you can see distinct GPS tracks when you zoom in at 100m level. Or if there is an automatic update request from Waze that suggests you add the turn lane. 10. When you are confident on an area you have mapped,'''&nbsp;lock the roads'''&nbsp;to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed &nbsp;and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits.'''&nbsp;Tollways and Major highways are to be locked to level 4'''&nbsp;because these will rarely change so will require little to no editing.&nbsp;'''Minor and Primary streets are to be locked to level 3'''&nbsp;so they can be managed by their respective Area Managers. Other streets are to be locket to level 3 at the discretion of the Area Managers responsible for them. 11.'''&nbsp;Adding Landmarks and Gas Stations'''; Waze doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark and Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile.'''&nbsp;''' 12.&nbsp;'''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than made complex, therefore&nbsp;simplicity&nbsp;should be a key goal in&nbsp;design&nbsp;and unnecessary complexity should be avoided. 6ba5a701c1a1d2afab60e7aefaa72cef925f87fd 10076 10075 2013-07-22T06:04:03Z Kazmuth 35 wikitext text/x-wiki 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads&nbsp;within a commercial or private parking lots, not used for routing except when destination is on the parking lot road. * Private Road – driveable roads&nbsp;within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the CITY of your edits. Unlike STREET names which reflects edits (or corrections) quicker and appears on the next update, CITY names unfortunately embeds much longer&nbsp;on the CITY tiles in the servers. So misspelled CITY names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the OFFICIAL (but shortest possible) NAME of the jurisdiction being edited. Also, if you are UNSURE of the POLITICAL BOUNDARIES of the "CITY" you are editing, leave it at that for the moment. let's leave it to the more experienced & knowledgeable editors to sort this mater out. Another matter of&nbsp;CITY&nbsp;labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are&nbsp;QUEZON, CEBU, DAVAO, CAVITE, etc as these cities have a&nbsp;provincial&nbsp;counterpart.&nbsp; This will distinguish&nbsp;Quezon City&nbsp;with the&nbsp;province of Quezon,&nbsp;Cebu City&nbsp;with the&nbsp;province of Cebu, so on & so forth. All other cities (& municipalities) will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P)&nbsp;for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9.&nbsp;'''Do not split roads unless'''&nbsp;they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road&nbsp;'''should'''&nbsp;be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road&nbsp;'''should not'''&nbsp;be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes - do not create dedicated turn lanes'''&nbsp;unless you can see distinct GPS tracks when you zoom in at 100m level. Or if there is an automatic update request from Waze that suggests you add the turn lane. 10. When you are confident on an area you have mapped,'''&nbsp;lock the roads'''&nbsp;to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed &nbsp;and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits.'''&nbsp;Tollways and Major highways are to be locked to level 4'''&nbsp;because these will rarely change so will require little to no editing.&nbsp;'''Minor and Primary streets are to be locked to level 3'''&nbsp;so they can be managed by their respective Area Managers. Other streets are to be locket to level 3 at the discretion of the Area Managers responsible for them. 11.'''&nbsp;Adding Landmarks and Gas Stations'''; Waze doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark and Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile.'''&nbsp;''' 12.&nbsp;'''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than made complex, therefore&nbsp;simplicity&nbsp;should be a key goal in&nbsp;design&nbsp;and unnecessary complexity should be avoided. e87cb573b873e9d2a5ff26542aea95aca175c51e 10077 10076 2013-07-22T07:01:52Z Kazmuth 35 wikitext text/x-wiki ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads&nbsp;within a commercial or private parking lots, not used for routing except when destination is on the parking lot road. * Private Road – driveable roads&nbsp;within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the CITY of your edits. Unlike STREET names which reflects edits (or corrections) quicker and appears on the next update, CITY names unfortunately embeds much longer&nbsp;on the CITY tiles in the servers. So misspelled CITY names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the OFFICIAL (but shortest possible) NAME of the jurisdiction being edited. Also, if you are UNSURE of the POLITICAL BOUNDARIES of the "CITY" you are editing, leave it at that for the moment. let's leave it to the more experienced & knowledgeable editors to sort this mater out. Another matter of&nbsp;CITY&nbsp;labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are&nbsp;QUEZON, CEBU, DAVAO, CAVITE, etc as these cities have a&nbsp;provincial&nbsp;counterpart.&nbsp; This will distinguish&nbsp;Quezon City&nbsp;with the&nbsp;province of Quezon,&nbsp;Cebu City&nbsp;with the&nbsp;province of Cebu, so on & so forth. All other cities (& municipalities) will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P)&nbsp;for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9.&nbsp;'''Do not split roads unless'''&nbsp;they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road&nbsp;'''should'''&nbsp;be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road&nbsp;'''should not'''&nbsp;be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes - do not create dedicated turn lanes'''&nbsp;unless you can see distinct GPS tracks when you zoom in at 100m level. Or if there is an automatic update request from Waze that suggests you add the turn lane. 10. When you are confident on an area you have mapped,'''&nbsp;lock the roads'''&nbsp;to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed &nbsp;and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits.'''&nbsp;Tollways and Major highways are to be locked to level 4'''&nbsp;because these will rarely change so will require little to no editing.&nbsp;'''Minor and Primary streets are to be locked to level 3'''&nbsp;so they can be managed by their respective Area Managers. Other streets are to be locket to level 3 at the discretion of the Area Managers responsible for them. 11.'''&nbsp;Adding Landmarks and Gas Stations'''; Waze doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark and Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile.'''&nbsp;''' 12.&nbsp;'''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than made complex, therefore&nbsp;simplicity&nbsp;should be a key goal in&nbsp;design&nbsp;and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and mark it as 'not identified' and save. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). 10f51bbc0076ef5c71ff8cfabd5ea1e8fcecda32 10078 10077 2013-07-22T13:31:16Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads&nbsp;within a commercial or private parking lots, not used for routing except when destination is on the parking lot road. * Private Road – driveable roads&nbsp;within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the CITY of your edits. Unlike STREET names which reflects edits (or corrections) quicker and appears on the next update, CITY names unfortunately embeds much longer&nbsp;on the CITY tiles in the servers. So misspelled CITY names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the OFFICIAL (but shortest possible) NAME of the jurisdiction being edited. Also, if you are UNSURE of the POLITICAL BOUNDARIES of the "CITY" you are editing, leave it at that for the moment. let's leave it to the more experienced & knowledgeable editors to sort this mater out. Another matter of&nbsp;CITY&nbsp;labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are&nbsp;QUEZON, CEBU, DAVAO, CAVITE, etc as these cities have a&nbsp;provincial&nbsp;counterpart.&nbsp; This will distinguish&nbsp;Quezon City&nbsp;with the&nbsp;province of Quezon,&nbsp;Cebu City&nbsp;with the&nbsp;province of Cebu, so on & so forth. All other cities (& municipalities) will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P)&nbsp;for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9.&nbsp;'''Do not split roads unless'''&nbsp;they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road&nbsp;'''should'''&nbsp;be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road&nbsp;'''should not'''&nbsp;be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes - do not create dedicated turn lanes'''&nbsp;unless you can see distinct GPS tracks when you zoom in at 100m level. Or if there is an automatic update request from Waze that suggests you add the turn lane. 10. When you are confident on an area you have mapped,'''&nbsp;lock the roads'''&nbsp;to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed &nbsp;and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits.'''&nbsp;Tollways and Major highways are to be locked to level 4'''&nbsp;because these will rarely change so will require little to no editing.&nbsp;'''Minor and Primary streets are to be locked to level 3'''&nbsp;so they can be managed by their respective Area Managers. Other streets are to be locket to level 3 at the discretion of the Area Managers responsible for them. 11.'''&nbsp;Adding Landmarks and Gas Stations'''; Waze doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark and Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile.'''&nbsp;''' 12.&nbsp;'''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than made complex, therefore&nbsp;simplicity&nbsp;should be a key goal in&nbsp;design&nbsp;and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and mark it as 'not identified' and save. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>baldugaras</td> <td>Luzon Island Group</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> </table> 35117da114d05c78683fa4cff5f8170b4802fbff 10079 10078 2013-07-23T02:11:24Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, not used for routing except when destination is on the parking lot road. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes - do not create dedicated turn lanes''' unless you can see distinct GPS tracks when you zoom in at 100m level. Or if there is an automatic update request from Waze that suggests you add the turn lane. 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and mark it as 'not identified' and save. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>baldugaras</td> <td>Luzon Island Group</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> </table> 32c3fafa5e4e1a80bc93080d8047274e22242de0 10080 10079 2013-07-28T06:32:12Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, not used for routing except when destination is on the parking lot road. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and mark it as 'not identified' and save. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>baldugaras</td> <td>Luzon Island Group</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> </table> 9335e6e94d94fa7a464cf487245342981e60740a 10081 10080 2013-08-04T01:19:09Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and mark it as 'not identified' and save. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>baldugaras</td> <td>Luzon Island Group</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> </table> 913002474eae4e210589de8dc579764ef442fcbf 10082 10081 2013-08-04T01:37:27Z Kazmuth 35 /* Philippine Waze Area Managers */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and mark it as 'not identified' and save. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>baldugaras</td> <td>Luzon Island Group</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> </table> 31bb01ec9e180c099058ae41a3e6e924d08c8cbd 10083 10082 2013-08-12T06:22:06Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>baldugaras</td> <td>Luzon Island Group</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> </table> 3ef9081f90d6da733c0581ec5fd7da26ce5415ba 10084 10083 2013-09-09T05:40:50Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>baldugaras</td> <td>Luzon Island Group</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> </table> 1d254d89a983f6d3f44becab9cbb2124645aa4a4 10085 10084 2013-09-09T05:46:37Z Kazmuth 35 /* Philippine Waze Area Managers */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>baldugaras</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> f7545ccf9bf6ce871c5c3dbfaa875510ab5e5419 10086 10085 2013-09-20T13:59:26Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>baldugaras</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 2982d222def9ae664654038a2c167ac70eab91a9 10087 10086 2013-09-20T14:09:30Z Kazmuth 35 /* Philippine Waze Area Managers */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 19af5f0e71e005ff956219a7b366845b82652745 10088 10087 2013-09-23T05:43:21Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 3 at the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 35caf546ae2c578040b23df7d81f8d445ffc7b2e 10089 10088 2013-10-10T07:55:07Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 12df88221351efde19bbbde2ccbc43d77f598f9f 10090 10089 2013-10-13T12:13:18Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 1396e5f5d8d02ca1eda3de4b91e5e38ac1e95ab5 10091 10090 2013-10-15T06:45:30Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 4d808fda188dbd1723d9d67ba2266ddcf0c4ddd7 10092 10091 2013-10-15T06:50:42Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or simply if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to SpeedZel, kazmuth, or rider111 of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 175da91799b862542f9d6d760f92a52b98298398 10093 10092 2013-10-19T02:33:56Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or simply if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 2b3b38ab55f17371f0bd81fb7d227e5ea416bf3b 10094 10093 2013-10-19T14:41:21Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Road that crosses multiple provinces * Minor Highway – Road that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or simply if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way, one way, dead end) 4. Set the level (ground level = 0, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change so will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 4e0455062d7fec57d6a6f542f34e1aac84896d7b 10095 10094 2013-10-19T15:07:50Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> 6a6c63a6a9c9b97bf4abc679bcdbfde6d8f9e0f8 10096 10095 2013-10-20T04:02:30Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) We have certain requirements to ensure that area managers know the basics of waze map editing including the Philippine map editing guide. Minimum requirement of 1k map updates for up to citywide areas. * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> </table> e907a7544e0b73b31f5f81c744cfa278a35fe303 10097 10096 2013-10-20T05:35:34Z Kazmuth 35 /* Philippine Waze Area Managers */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) We have certain requirements to ensure that area managers know the basics of waze map editing including the Philippine map editing guide. Minimum requirement of 1k map updates for up to citywide areas. * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> <td>crgandionco</td> <td>Leyte, Samar</td> <tr> </tr> <td>walkingmap</td> <td>Las Pinas / Luzon area</td> <tr> </tr> <td>ivanatorprime</td> <td>Mandaluyong</td> <tr> </tr> </table> 10f3bca361a2d5d218bc51d42e041744d10b0fc4 10098 10097 2013-10-20T05:41:13Z Kazmuth 35 /* Philippine Waze Area Managers */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) We have certain requirements to ensure that area managers know the basics of waze map editing including the Philippine map editing guide. Minimum requirement of 1k map updates for up to citywide areas. * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> <td>crgandionco</td> <td>Leyte, Samar</td> <tr> </tr> <td>walkingmap</td> <td>Las Pinas / Luzon area</td> <tr> </tr> <td>ivanatorprime</td> <td>Mandaluyong</td> <tr> </tr> </table> f3d034d6e8714abaf5dcf955cda25a14dfec5856 10099 10098 2013-10-21T06:26:04Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Areas which are more than 90% complete and accurate can be locked to the highest level. This is to minimize vandalism or accidental edits. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) We have certain requirements to ensure that area managers know the basics of waze map editing including the Philippine map editing guide. Minimum requirement of 1k map updates for up to citywide areas. * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> <td>crgandionco</td> <td>Leyte, Samar</td> <tr> </tr> <td>walkingmap</td> <td>Las Pinas / Luzon area</td> <tr> </tr> <td>ivanatorprime</td> <td>Mandaluyong</td> <tr> </tr> </table> 0e329db11feb85fc6db485982d7641333740a23e 10100 10099 2013-10-30T03:33:10Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate can be locked to the highest level. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) We have certain requirements to ensure that area managers know the basics of waze map editing including the Philippine map editing guide. Minimum requirement of 1k map updates for up to citywide areas. * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Level 5)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Level 4)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> <td>crgandionco</td> <td>Leyte, Samar</td> <tr> </tr> <td>walkingmap</td> <td>Las Pinas / Luzon area</td> <tr> </tr> <td>ivanatorprime</td> <td>Mandaluyong</td> <tr> </tr> </table> 8a3de3bec6fe83b481c89ca55f58ae4a0a851b5f 10101 10100 2013-11-13T03:25:27Z Kazmuth 35 /* Philippine Waze Area Managers */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate can be locked to the highest level. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) We have certain requirements to ensure that area managers know the basics of waze map editing including the Philippine map editing guide. Minimum requirement of 1k map updates for up to citywide areas. * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. <table border="1"> <tr> <th>Waze Username</th> <th>Area</th> </tr> <tr> <td>'''rider111 (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>RenzDeion</td> <td>Pampanga</td> <tr> </tr> <td>gerix28</td> <td>Cebu</td> <tr> </tr> <td>atjcamacho</td> <td>NCR and Cavite</td> <tr> </tr> <td>markking1991</td> <td>Manila</td> <tr> </tr> <td>furuboru</td> <td>NCR</td> <tr> </tr> <td>junrex</td> <td>Region V</td> <tr> </tr> <td>'''SpeedDzel (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>iceden</td> <td>Philippines</td> <tr> </tr> <td>monz98</td> <td>Eastern NCR</td> <tr> </tr> <td>monz98</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>gerix28</td> <td>Region VII</td> <tr> </tr> <td>'''baldugaras (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>Ungas</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>Calicantzaros</td> <td>Central Luzon (Region III)</td> <tr> </tr> <td>Calicantzaros</td> <td>NCR</td> <tr> </tr> <td>BRM-BLK-BMW</td> <td>NCR and Cavite</td> <tr> </tr> <td>bdo2v</td> <td>NCR</td> <tr> </tr> <td>ericbishop</td> <td>CALABARZON (Region IV-A)</td> <tr> </tr> <td>SkipperBoo26</td> <td>NCR</td> <tr> </tr> <td>pinoyoutdoor</td> <td>Cebu</td> <tr> </tr> <td>M-a-r-s</td> <td>NCR and Bislig City</td> <tr> </tr> <td>nobs98</td> <td>Region VII</td> <tr> </tr> <td>'''kazmuth (Country Manager)'''</td> <td>Philippines</td> <tr> </tr> <td>evs_13</td> <td>Pangasinan</td> <tr> </tr> <td>world_8eidg3mz</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>world_32m24hzt</td> <td>Cebu City</td> <tr> </tr> <td>kid_ant</td> <td>Cabanatuan City</td> <tr> </tr> <td>abecedarian2380</td> <td>Cebu</td> <tr> </tr> <td>foruboru</td> <td>Luzon Island Group</td> <tr> </tr> <td>warfab</td> <td>Mandaue and Cebu City</td> <tr> </tr> <td>mirallwood</td> <td>NCR</td> <tr> </tr> <td>mponteres</td> <td>Muntinlupa and Cabuyao</td> <tr> </tr> <td>markhaggai</td> <td>Puerto Princesa</td> <tr> </tr> <td>ongandy86</td> <td>Quezon City</td> <tr> </tr> <td>crgandionco</td> <td>Leyte, Samar</td> <tr> </tr> <td>walkingmap</td> <td>Las Pinas / Luzon area</td> <tr> </tr> <td>ivanatorprime</td> <td>Mandaluyong</td> <tr> </tr> </table> 8eaf34729b510ee3e9dd1223e481a3a5be1325da 10102 10101 2013-11-13T03:57:33Z Kazmuth 35 /* Philippine Waze Area Managers */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate can be locked to the highest level. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level 4''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) We have certain requirements to ensure that area managers know the basics of waze map editing including the Philippine map editing guide. Minimum requirement of 1k map updates for up to citywide areas. * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |} 5a650c9a4a9d157d5ea0f250578dc36f53d755c5 10103 10102 2013-11-17T03:00:15Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) We have certain requirements to ensure that area managers know the basics of waze map editing including the Philippine map editing guide. Minimum requirement of 1k map updates for up to citywide areas. * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. These I immediately mark "Not identified" because I don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or “Not identified” if it needs more information. Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |} eedfc1e6dc5b306b77814eda131566c28fb42570 10104 10103 2013-11-18T06:48:46Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) We have certain requirements to ensure that area managers know the basics of waze map editing including the Philippine map editing guide. Minimum requirement of 1k map updates for up to citywide areas. * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. You can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified" because we don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or you can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified". Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, just leave a comment asking for one so that the reporter can help you fix the issue. Only close URs when you don't receive a reply after 7 days, after then you can mark these as Not identified. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |} 857bb53fe197f9623be5edd04f355a3832831f71 10105 10104 2013-12-29T09:29:27Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. You can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified" because we don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or you can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified". Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, just leave a comment asking for one so that the reporter can help you fix the issue. Only close URs when you don't receive a reply after 7 days, after then you can mark these as Not identified. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Managers== This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |} 8c87c81fc336fef47e7f488f57c3a799530db655 10106 10105 2013-12-29T09:34:48Z Kazmuth 35 /* Philippine Waze Area Managers */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. You can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified" because we don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or you can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified". Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, just leave a comment asking for one so that the reporter can help you fix the issue. Only close URs when you don't receive a reply after 7 days, after then you can mark these as Not identified. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied - City wide or permalink wide - 1k for provincial and 5k map edits for NCR - Province wide - 20k map edits - Region wide - 50k map edits - Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 - Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |} 7af4fb8b595de86eb9bdb88fece305a5ccca83ee 10107 10106 2013-12-29T09:37:45Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. You can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified" because we don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or you can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified". Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, just leave a comment asking for one so that the reporter can help you fix the issue. Only close URs when you don't receive a reply after 7 days, after then you can mark these as Not identified. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |} 410a0bf5e4aea91452a81a7454973be5be1274e7 10108 10107 2013-12-29T09:52:24Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. You can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified" because we don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or you can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified". Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, just leave a comment asking for one so that the reporter can help you fix the issue. Only close URs when you don't receive a reply after 7 days, after then you can mark these as Not identified. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |} 1d6b2332d22f6281eb8b74d4d49ae79091d9f2d7 10109 10108 2013-12-31T12:38:24Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; '''NOTE: When resolving issues, always put a comment on what you did on the map''' The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. You can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified" because we don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or you can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified". Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, just leave a comment asking for one so that the reporter can help you fix the issue. Only close URs when you don't receive a reply after 7 days, after then you can mark these as Not identified. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and restrict the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). There are some exceptions; in particular, where restricting these turns would eliminate all possible entries to a major commuter route. For example, where a commuter road is one-way during rush hours, in opposite directions, turns onto that road should not be restricted even though those turns are prohibited during certain hours of the day. One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |} 87f62095b4a47a3a51c3c5a4bd856842fb49a758 0 2 10110 10109 2014-01-06T08:29:38Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''How do I fix Update Requests?''' User submitted Update Requests are more difficult to fix because they might not contain enough information or there might not really by a map issue. The most common update requests are 'General Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is really nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. Here are the different types of update requests, they are; General error, Turn not allowed, Incorrect junction, Missing bridge or overpass, Wrong driving directions, Missing exit, and Missing road. Here are some suggestions on how to resolve these issues; '''NOTE: When resolving issues, always put a comment on what you did on the map''' The first is the vague "General error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. You can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified" because we don't know what the map issue is about. The reporter will receive a notification email and could edit the map themselves if it is indeed an issue. Some "General error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or you can leave a comment to ask for more details. If there is no reply within a week you can mark these as "Not identified". Other valid "General error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, just leave a comment asking for one so that the reporter can help you fix the issue. Only close URs when you don't receive a reply after 7 days, after then you can mark these as Not identified. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |} 08a07f274eca6b7ffb76b2409aab6df2eb8c2b84 10111 10110 2014-01-24T07:32:23Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |- | daxky | NCR |- | daxky | Batangas City |- | daxky | Angeles City |- | daxky | Lipa City |- | crgandionco | Southern Leyte |- | RegieTagavilla | Region 9 |- | RegieTagavilla | Region 10 |- | RegieTagavilla | Region 11 |- | RegieTagavilla | Region 12 |- | RegieTagavilla | Region 13 |- | RegieTagavilla | ARMM (Area 1) |- | RegieTagavilla | ARMM (Area 2) |- | daxky | Boracay Island |- | M-a-r-s | Easter Mindanao |- | tcajita | Calamba |- | tcajita | Sta Rosa |- | kwithoor | Sta Rosa |- | kwithoor | Region 3 |- | tcajita | NCR |- | RangeRoverHSE | NCR |- | bgaltman | NCR |} 80ecc7d72707d0fc70d6feb34557adc207510e10 10112 10111 2014-01-24T07:39:32Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |- | daxky | NCR |- | daxky | Batangas City |- | daxky | Angeles City |- | daxky | Lipa City |- | crgandionco | Southern Leyte |- | RegieTagavilla | Region 9 |- | RegieTagavilla | Region 10 |- | RegieTagavilla | Region 11 |- | RegieTagavilla | Region 12 |- | RegieTagavilla | Region 13 |- | RegieTagavilla | ARMM (Area 1) |- | RegieTagavilla | ARMM (Area 2) |- | daxky | Boracay Island |- | M-a-r-s | Easter Mindanao |- | tcajita | Calamba |- | tcajita | Sta Rosa |- | kwithoor | Region 3 |- | kwithoor | NCR |- | RangeRoverHSE | NCR |- | bgaltman | NCR |} 3082fe01c7c625119fa511d0dd52c605e9c4d84e 10113 10112 2014-01-24T07:43:12Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |- | daxky | NCR |- | daxky | Batangas City |- | daxky | Angeles City |- | daxky | Lipa City |- | crgandionco | Southern Leyte |- | RegieTagavilla | Region 9 |- | RegieTagavilla | Region 10 |- | RegieTagavilla | Region 11 |- | RegieTagavilla | Region 12 |- | RegieTagavilla | Region 13 |- | RegieTagavilla | ARMM (Area 1) |- | RegieTagavilla | ARMM (Area 2) |- | daxky | Boracay Island |- | M-a-r-s | Easter Mindanao |- | tcajita | Calamba |- | tcajita | Sta Rosa |- | kwithoor | Region 3 |- | kwithoor | NCR |- | RangeRoverHSE | NCR |- | bgaltman | NCR |} e14e440e93bd2da3073989ae21b1a47a83fd947e 10114 10113 2014-01-24T07:51:01Z Kazmuth 35 /* Guidelines for Resolving Update Requests (UR) */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- ! Waze Username ! Area |- | '''rider111 (Country Manager)''' | Philippines |- | RenzDeion | Pampanga |- | gerix28 | Cebu |- | atjcamacho | NCR and Cavite |- | markking1991 | Manila |- | furuboru | NCR |- | junrex | Region V |- | '''SpeedDzel (Country Manager)''' | Philippines |- | iceden | Philippines |- | monz98 | Eastern NCR |- | monz98 | CALABARZON (Region IV-A) |- | gerix28 | Region VII |- | '''baldugaras (Country Manager)''' | Philippines |- | Ungas | CALABARZON (Region IV-A) |- | Calicantzaros | Central Luzon (Region III) |- | Calicantzaros | NCR |- | BRM-BLK-BMW | NCR and Cavite |- | bdo2v | NCR |- | ericbishop | CALABARZON (Region IV-A) |- | SkipperBoo26 | NCR |- | pinoyoutdoor | Cebu |- | M-a-r-s | NCR and Bislig City |- | nobs98 | Region VII |- | '''kazmuth (Country Manager)''' | Philippines |- | evs_13 | Pangasinan |- | world_8eidg3mz | Mandaue and Cebu City |- | world_32m24hzt | Cebu City |- | kid_ant | Cabanatuan City |- | abecedarian2380 | Cebu |- | foruboru | Luzon Island Group |- | warfab | Mandaue and Cebu City |- | mirallwood | NCR |- | mponteres | Muntinlupa and Cabuyao |- | markhaggai | Puerto Princesa |- | ongandy86 | Quezon City |- | crgandionco | Leyte, Samar |- | walkingmap | Las Pinas / Luzon Island Group |- | ivanatorprime | Mandaluyong |- | daxky | NCR |- | daxky | Batangas City |- | daxky | Angeles City |- | daxky | Lipa City |- | crgandionco | Southern Leyte |- | RegieTagavilla | Region 9 |- | RegieTagavilla | Region 10 |- | RegieTagavilla | Region 11 |- | RegieTagavilla | Region 12 |- | RegieTagavilla | Region 13 |- | RegieTagavilla | ARMM (Area 1) |- | RegieTagavilla | ARMM (Area 2) |- | daxky | Boracay Island |- | M-a-r-s | Easter Mindanao |- | tcajita | Calamba |- | tcajita | Sta Rosa |- | kwithoor | Region 3 |- | kwithoor | NCR |- | RangeRoverHSE | NCR |- | bgaltman | NCR |} efe52daf4e0836502123e68dc78476bc15250436 10115 10114 2014-01-29T09:30:28Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles City||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig City||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan City||8/2/2013 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite||6/23/2013 |- | abecedarian2380|| Cebu||8/2/2013 |- | gerix28|| Cebu||6/22/2013 |- | pinoyoutdoor|| Cebu||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Easter Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa City||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR and Cavite||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} b59a6498606d69b95d9c46da0ec8d9e107988d73 10116 10115 2014-01-31T05:55:21Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Easter Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} c781294a67155a99dbbfbbff46d6c0036d0d0038 10117 10116 2014-01-31T05:57:53Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Easter Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' e39cace5dd858cd7c5adf73869a1c51fca1df929 10118 10117 2014-02-04T01:40:30Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Metro Manila, Rizal, Bulacan, Cavite and other areas which are more than 90% complete and accurate, ordinary streets can be locked to the level 3. Minor Highways and Primary roads can also be locked to level 4 on these areas. This is to minimize vandalism or accidental edits. Unnamed roads should not be locked so that they can be edited and named by anyone. '''Tollways and Major highways are to be locked to level to the highest level''' because these will rarely change and will require little to no editing. '''Minor and Primary streets are to be locked to level 3''' so they can be managed by their respective Area Managers. Other streets are to be locked to level 2 or 3, except for private roads inside subdivisions. Locking these are left to the discretion of the Area Managers responsible for them. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 60b8c36a0b5fb7b9787564be6a2520599feaf9c2 10119 10118 2014-02-09T03:33:13Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; 1. Already 90% complete and accurate. 2. Changes or edits to these segments are seldom done or does not happen that often. 3. Segments that are high value roads where incorrect edits will result in routing issues. 4. Vandalism on the Waze maps 5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 7c0a50cf6317117556c50a5603813940a5a7b1c7 10120 10119 2014-02-09T03:36:47Z Kazmuth 35 /* Philippine Locking Policy */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 94052b1e8faf2f9eea22a3443054123ed9352734 10121 10120 2014-02-13T12:21:52Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 1k for provincial and 5k map edits for NCR ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - 250k map edits or level 5 * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 10883d30232c5f0ef091c0ef9a5b1cdf2204be74 10122 10121 2014-02-17T06:29:26Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** NCR wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' a534c70aef375057be47eec0b8d0e550eeb28dd2 10123 10122 2014-02-18T13:54:10Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 4e23a4f6a0a68ac931281d770bf1619fcae5edf6 10124 10123 2014-02-18T14:06:23Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | proletaryo|| Bacolod, Silay||2/17/2014 |- | shogsbro|| Baguio||2/17/2014 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | proletaryo|| Kabankalan, Ilog ||2/17/2014 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | proletaryo|| CALABARZON (Region IV-A)||2/17/2014 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | proletaryo|| Iloilo City||2/17/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | proletaryo|| NCR ||2/17/2014 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' a14ab9713b127d9f5e208672c28bb2fd51891bd8 10125 10124 2014-02-26T05:20:12Z Kazmuth 35 /* Philippine Locking Policy */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | proletaryo|| Bacolod, Silay||2/17/2014 |- | shogsbro|| Baguio||2/17/2014 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | proletaryo|| Kabankalan, Ilog ||2/17/2014 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | proletaryo|| CALABARZON (Region IV-A)||2/17/2014 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | proletaryo|| Iloilo City||2/17/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | proletaryo|| NCR ||2/17/2014 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 7c970173f383fb065f970ce223921d77c5c76529 10126 10125 2014-03-03T06:18:35Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | proletaryo|| Bacolod, Silay||2/17/2014 |- | shogsbro|| Baguio||2/17/2014 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | proletaryo|| Kabankalan, Ilog ||2/17/2014 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | proletaryo|| CALABARZON (Region IV-A)||2/17/2014 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | proletaryo|| Iloilo City||2/17/2014 |- | proletaryo|| Iloilo Province ||3/3/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | proletaryo|| NCR ||2/17/2014 |- | proletaryo|| Negros Occidental Province ||3/3/2014 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | bgaltman|| Pangasinan||7/12/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 478b26a55a1713a3943caad6f2343dde4288a359 10127 10126 2014-03-12T12:56:32Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | proletaryo|| Bacolod, Silay||2/17/2014 |- | shogsbro|| Baguio||2/17/2014 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | proletaryo|| Kabankalan, Ilog ||2/17/2014 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | proletaryo|| CALABARZON (Region IV-A)||2/17/2014 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | proletaryo|| Iloilo City||2/17/2014 |- | proletaryo|| Iloilo Province ||3/3/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | proletaryo|| NCR ||2/17/2014 |- | proletaryo|| Negros Occidental Province ||3/3/2014 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | bgaltman|| Pangasinan||7/12/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' beee8edb8a9032f1ac30a2c11e4cc4ed51fb6a81 10128 10127 2014-03-12T12:57:22Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="1" |- |''' Waze Username'''||''' Area'''||'''Since''' |- | daxky|| Angeles ||11/18/2013 |- | RegieTagavilla|| ARMM (Area 1)||12/30/2013 |- | RegieTagavilla|| ARMM (Area 2)||12/30/2013 |- | proletaryo|| Bacolod, Silay||2/17/2014 |- | shogsbro|| Baguio||2/17/2014 |- | daxky|| Batangas City||11/18/2013 |- | junrex|| Bicol (Region V)||6/24/2013 |- | M-a-r-s|| Bislig ||8/22/2013 |- | daxky|| Boracay Island||12/31/2013 |- | kid_ant|| Cabanatuan ||8/2/2013 |- | proletaryo|| Kabankalan, Ilog ||2/17/2014 |- | mponteres|| Cabuyao||8/22/2013 |- | ericbishop|| CALABARZON (Region IV-A)||7/5/2013 |- | monz98|| CALABARZON (Region IV-A)||6/28/2013 |- | Ungas|| CALABARZON (Region IV-A)||6/29/2013 |- | proletaryo|| CALABARZON (Region IV-A)||2/17/2014 |- | tcajita|| Calamba||1/11/2014 |- | RegieTagavilla|| Caraga (Region XIII)||12/30/2013 |- | atjcamacho|| Cavite Province||6/23/2013 |- | BRM-BLK-BMW|| Cavite Province||7/4/2013 |- | abecedarian2380|| Cebu Province||8/2/2013 |- | gerix28|| Cebu Province||6/22/2013 |- | pinoyoutdoor|| Cebu Province||7/7/2013 |- | warfab|| Cebu City||8/14/2013 |- | world_32m24hzt|| Cebu City||7/26/2013 |- | world_8eidg3mz|| Cebu City||7/20/2013 |- | Calicantzaros|| Central Luzon (Region III)||7/2/2013 |- | kwithoor|| Central Luzon (Region III)||1/11/2014 |- | SEELE_01|| Central Luzon (Region III)||1/29/2014 |- | gerix28|| Central Visayas (Region VII)||6/28/2013 |- | nobs98|| Central Visayas (Region VII)||7/8/2013 |- | RegieTagavilla|| Davao (Region XI)||12/30/2013 |- | M-a-r-s|| Eastern Mindanao||12/5/2013 |- | monz98|| Eastern NCR||6/27/2013 |- | RangeRoverHSE|| Eastern Visayas (Region VIII)||1/27/2014 |- | proletaryo|| Iloilo City||2/17/2014 |- | proletaryo|| Iloilo Province ||3/3/2014 |- | RegieTagavilla|| Las Pinas||9/9/2013 |- | crgandionco|| Leyte||9/9/2013 |- | daxky|| Lipa ||1/18/2013 |- | foruboru|| Luzon Island Group||8/8/2013 |- | RegieTagavilla|| Luzon Island Group||9/9/2013 |- | ivanatorprime|| Mandaluyong||10/11/2013 |- | warfab|| Mandaue||8/14/2013 |- | world_8eidg3mz|| Mandaue||7/20/2013 |- | markking1991|| Manila||6/23/2013 |- | mponteres|| Muntinlupa||8/22/2013 |- | atjcamacho|| NCR||6/23/2013 |- | bdo2v|| NCR||7/4/2013 |- | bgaltman|| NCR||1/11/2014 |- | Calicantzaros|| NCR||7/2/2013 |- | daxky|| NCR||11/18/2013 |- | furuboru|| NCR||6/23/2013 |- | kwithoor|| NCR||1/11/2014 |- | M-a-r-s|| NCR||7/7/2013 |- | mirallwood|| NCR||8/18/2013 |- | RangeRoverHSE|| NCR||1/11/2014 |- | SEELE_01|| NCR||1/29/2014 |- | SkipperBoo26|| NCR||7/7/2013 |- | BRM-BLK-BMW|| NCR ||7/4/2013 |- | proletaryo|| NCR ||2/17/2014 |- | proletaryo|| Negros Occidental Province ||3/3/2014 |- | RegieTagavilla|| Northern Mindanao (Region X)||12/30/2013 |- | RenzDeion|| Pampanga||6/22/2013 |- | bgaltman|| Pangasinan||7/12/2013 |- | evs_13|| Pangasinan||7/12/2013 |- | '''baldugaras (Country Manager)'''|| Philippines||8/7/2013 |- | iceden|| Philippines||6/25/2013 |- | '''kazmuth (Country Manager)'''|| Philippines||11/13/2012 |- | '''rider111 (Country Manager)'''|| Philippines||6/21/2013 |- | '''SpeedDzel (Country Manager)'''|| Philippines||11/13/2012 |- | markhaggai|| Puerto Princesa||8/30/2013 |- | ongandy86|| Quezon City||8/30/2013 |- | crgandionco|| Samar||9/9/2013 |- | RegieTagavilla|| SOCCSKSARGEN (Region XII)||12/30/2013 |- | crgandionco|| Southern Leyte||12/21/2013 |- | tcajita|| Sta Rosa||1/11/2014 |- | RegieTagavilla|| Zamboanga Peninsula (Region IX)||12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 4150d515bd9bfa3802dc7fa34b7ea7e0ab5209af 10129 10128 2014-03-12T13:21:49Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | ''' Waze Username''' ! scope="col" | ''' Area''' ! scope="col" | '''Since''' |- ! scope="col" | daxky | Angeles | 11/18/2013 |- ! scope="col" | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- ! scope="col" | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- ! scope="col" | proletaryo | Bacolod, Silay | 2/17/2014 |- ! scope="col" | shogsbro | Baguio | 2/17/2014 |- ! scope="col" | daxky | Batangas City | 11/18/2013 |- ! scope="col" | junrex | Bicol (Region V) | 6/24/2013 |- ! scope="col" | M-a-r-s | Bislig | 8/22/2013 |- ! scope="col" | daxky | Boracay Island | 12/31/2013 |- ! scope="col" | kid_ant | Cabanatuan | 8/2/2013 |- ! scope="col" | proletaryo | Kabankalan, Ilog | 2/17/2014 |- ! scope="col" | mponteres | Cabuyao | 8/22/2013 |- ! scope="col" | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- ! scope="col" | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- ! scope="col" | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- ! scope="col" | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- ! scope="col" | tcajita | Calamba | 1/11/2014 |- ! scope="col" | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- ! scope="col" | atjcamacho | Cavite Province | 6/23/2013 |- ! scope="col" | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- ! scope="col" | abecedarian2380 | Cebu Province | 8/2/2013 |- ! scope="col" | gerix28 | Cebu Province | 6/22/2013 |- ! scope="col" | pinoyoutdoor | Cebu Province | 7/7/2013 |- ! scope="col" | warfab | Cebu City | 8/14/2013 |- ! scope="col" | world_32m24hzt | Cebu City | 7/26/2013 |- ! scope="col" | world_8eidg3mz | Cebu City | 7/20/2013 |- ! scope="col" | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- ! scope="col" | kwithoor | Central Luzon (Region III) | 1/11/2014 |- ! scope="col" | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- ! scope="col" | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- ! scope="col" | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- ! scope="col" | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- ! scope="col" | M-a-r-s | Eastern Mindanao | 12/5/2013 |- ! scope="col" | monz98 | Eastern NCR | 6/27/2013 |- ! scope="col" | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- ! scope="col" | proletaryo | Iloilo City | 2/17/2014 |- ! scope="col" | proletaryo | Iloilo Province | 3/3/2014 |- ! scope="col" | RegieTagavilla | Las Pinas | 9/9/2013 |- ! scope="col" | crgandionco | Leyte | 9/9/2013 |- ! scope="col" | daxky | Lipa | 1/18/2013 |- ! scope="col" | foruboru | Luzon Island Group | 8/8/2013 |- ! scope="col" | RegieTagavilla | Luzon Island Group | 9/9/2013 |- ! scope="col" | ivanatorprime | Mandaluyong | 10/11/2013 |- ! scope="col" | warfab | Mandaue | 8/14/2013 |- ! scope="col" | world_8eidg3mz | Mandaue | 7/20/2013 |- ! scope="col" | markking1991 | Manila | 6/23/2013 |- ! scope="col" | mponteres | Muntinlupa | 8/22/2013 |- ! scope="col" | atjcamacho | NCR | 6/23/2013 |- ! scope="col" | bdo2v | NCR | 7/4/2013 |- ! scope="col" | bgaltman | NCR | 1/11/2014 |- ! scope="col" | Calicantzaros | NCR | 7/2/2013 |- ! scope="col" | daxky | NCR | 11/18/2013 |- ! scope="col" | furuboru | NCR | 6/23/2013 |- ! scope="col" | kwithoor | NCR | 1/11/2014 |- ! scope="col" | M-a-r-s | NCR | 7/7/2013 |- ! scope="col" | mirallwood | NCR | 8/18/2013 |- ! scope="col" | RangeRoverHSE | NCR | 1/11/2014 |- ! scope="col" | SEELE_01 | NCR | 1/29/2014 |- ! scope="col" | SkipperBoo26 | NCR | 7/7/2013 |- ! scope="col" | BRM-BLK-BMW | NCR | 7/4/2013 |- ! scope="col" | proletaryo | NCR | 2/17/2014 |- ! scope="col" | proletaryo | Negros Occidental Province | 3/3/2014 |- ! scope="col" | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- ! scope="col" | RenzDeion | Pampanga | 6/22/2013 |- ! scope="col" | bgaltman | Pangasinan | 7/12/2013 |- ! scope="col" | evs_13 | Pangasinan | 7/12/2013 |- ! scope="col" | '''baldugaras (Country Manager)''' | Philippines | 8/7/2013 |- ! scope="col" | iceden | Philippines | 6/25/2013 |- ! scope="col" | '''kazmuth (Country Manager)''' | Philippines | 11/13/2012 |- ! scope="col" | '''rider111 (Country Manager)''' | Philippines | 6/21/2013 |- ! scope="col" | '''SpeedDzel (Country Manager)''' | Philippines | 11/13/2012 |- ! scope="col" | markhaggai | Puerto Princesa | 8/30/2013 |- ! scope="col" | ongandy86 | Quezon City | 8/30/2013 |- ! scope="col" | crgandionco | Samar | 9/9/2013 |- ! scope="col" | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- ! scope="col" | crgandionco | Southern Leyte | 12/21/2013 |- ! scope="col" | tcajita | Sta Rosa | 1/11/2014 |- ! scope="col" | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 7e94797a95c9b58d92bfc46a6d2b166349184386 10130 10129 2014-03-13T06:01:08Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 1/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras ''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth ''' | Philippines | 11/13/2012 |- | '''* rider111 ''' | Philippines | 6/21/2013 |- | '''* SpeedDzel ''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' e9858696b8e83b07bda2d622b644a73905b20b64 10131 10130 2014-03-13T06:02:03Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras ''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth ''' | Philippines | 11/13/2012 |- | '''* rider111 ''' | Philippines | 6/21/2013 |- | '''* SpeedDzel ''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' eb56652c935a5ee1e2cbbce0a79840248cd5c2d8 10132 10131 2014-03-13T06:05:01Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras ''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth ''' | Philippines | 11/13/2012 |- | '''* rider111 ''' | Philippines | 6/21/2013 |- | '''* SpeedDzel ''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' be68fca8190c65e269b1a1deb8086f5960511c5c 10133 10132 2014-03-15T02:32:41Z Kazmuth 35 /* Philippine Locking Policy */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. * Makati * Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras ''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth ''' | Philippines | 11/13/2012 |- | '''* rider111 ''' | Philippines | 6/21/2013 |- | '''* SpeedDzel ''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 01db25b59be0d65f064d5b38fab7514a6e711ab6 10134 10133 2014-03-15T02:39:23Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. If you want to check if you may have missed a turn restriction on a road network you have created, zoom back a bit and hit 'Shift+Z' on your keyboard. This will toggle the map to display all disabled turns. Hit 'Shift-Z' again to return to normal. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. * Makati * Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras ''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth ''' | Philippines | 11/13/2012 |- | '''* rider111 ''' | Philippines | 6/21/2013 |- | '''* SpeedDzel ''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 4a71f1d9db362d5a6954a1b07e1be7088bcc2066 10135 10134 2014-03-24T09:37:08Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ ==Map Editing Guide for the Philippines== 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Expressways and Toll Roads * Major Highway – Roads that crosses multiple provinces * Minor Highway – Roads that crosses multiple cities or municipalities * Ramps – On and off ramps from Freeways * Primary Street – Main thoroughfares of a city or municipality * Street – ordinary street, mainly residential * Service Roads – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) * Dirt-roads / 4x4 Trails – driveable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. * Parking Lot Road – driveable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. * Private Road – driveable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = -1, Flyover = 1, 2, 3, etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". Eg. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should contain the City or the Municipal name NOT THE AREA OR BARANGAY NAME.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this mater out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have provincial counterpart. This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently there is a Waze issues with cities with duplicate names. To address that issue, the city or municipality's provice's initial is added to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. For a complete list, refer to this list of [https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names] for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.''' Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==Guidelines for Resolving Update Requests (UR)== * '''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs * '''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. * '''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. 7 days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved ==Philippine Locking Policy== *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. * Makati * Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways''' Expressways are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways''' Major highways should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways''' Minor highways are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets''' Primary streets are should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads''' Railroads should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. ==Other Questions and Tips for the Pinoy Waze Editor== Here are the most asked questions from Pinoy Waze Editors * '''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * '''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]s. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :) * '''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area * '''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph * '''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. * '''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. * '''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. * '''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. * '''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. * '''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] * '''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. * '''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. * '''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. * '''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. * '''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. * '''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). * '''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: * If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. * The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. * The road will be opened when a number of users drive through the road. ==Philippine Waze Area Manager== '''What is an Area Manager and what does it entail:''' * An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. * Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. '''The following are the conditions or requirements for approval of AM applications:''' * Approval of at least 3 current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. * Meets X number of edits for area applied ** City wide or permalink wide - 5k map edits ** Metro Manila, Metro Cebu, and Metro Davao wide - 10k map edits ** Province wide - 20k map edits ** Region wide - 50k map edits ** Luzon, Visayas, or Mindanao Island Groups - 100k map edits or level 4 ** Countrywide - CM only * Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense) * Must have resolved at least 100 update requests * Must have at least 2500 existing kilometers * Must be an active member of the Waze forum and/or FB group page * Must attend at least 1 waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila * Must pass an online exam. (Currently under process) '''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras ''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth ''' | Philippines | 11/13/2012 |- | '''* rider111 ''' | Philippines | 6/21/2013 |- | '''* SpeedDzel ''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 8e1ce6f438762bb3db42b9b49d5f9a382da82758 10149 10148 2014-05-03T02:26:25Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the Update Request closing policy *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. *Makati *Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' e69a4ec5e5ab10e856be792eb418eb26ddc03eb2 10150 10149 2014-05-03T02:27:20Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. *Makati *Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 3d06bb489e15c13c46ce7c870e96e10fdfe732c8 10151 10150 2014-05-13T03:32:44Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. *Makati *Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 8bd959e3c3b68f4cbf11d5c9f54e69bea1d14763 10152 10151 2014-05-23T04:52:16Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. *Makati *Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' de879df41af540a6a2a8a55cb335e3521583705d 10153 10152 2014-05-23T05:04:00Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, do not map these roads unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. *Makati *Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 3890ea786384fd79506f1be43d1c3d50d8e3beea 10154 10153 2014-05-23T05:04:52Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. *Makati *Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 79663a662c9a048db6f78d61622e2bb6f7dad6dc 10157 10156 2014-05-24T00:03:54Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. *Makati *Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | RegieTagavilla | ARMM (Area 1) | 12/30/2013 |- | RegieTagavilla | ARMM (Area 2) | 12/30/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | RegieTagavilla | Caraga (Region XIII) | 12/30/2013 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | RegieTagavilla | Davao (Region XI) | 12/30/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | RegieTagavilla | Las Pinas | 9/9/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | RegieTagavilla | Luzon Island Group | 9/9/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RegieTagavilla | Northern Mindanao (Region X) | 12/30/2013 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | RegieTagavilla | SOCCSKSARGEN (Region XII) | 12/30/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | RegieTagavilla | Zamboanga Peninsula (Region IX) | 12/30/2013 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 4730ca15d85c24f3e5ea4e67bdd395410ebf8d35 10158 10157 2014-05-27T10:49:05Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 90% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and L3 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 90% map coverage and have roads locked to Level 5. *Makati *Pasig *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 8b09fbdd475131bf636fac291b3fce7fd5578e55 10159 10158 2014-05-28T13:02:44Z Kazmuth 35 /* Philippine Locking Policy */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 5.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 602747d3cdc672929a2df23d9ff1e4df215a8618 10160 10159 2014-05-29T04:59:05Z Kazmuth 35 /* Philippine Locking Policy */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. Stop reporting them because they will only get deleted. Speed cameras need to be approved before they show up on Waze, the only approved speed cameras so far are on NLEX and Commonwealth Avenue. If you are sure of a speed trap camera (static), identify the location on Waze and send a message to an Area Manager of the location and we will approve them. *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 5a0d3bf458e56e91cbee5222c41b29cb4bfb512b 10161 10160 2014-06-30T06:01:31Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | proletaryo | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | proletaryo | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | proletaryo | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | proletaryo | Iloilo City | 2/17/2014 |- | proletaryo | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | bgaltman | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | proletaryo | NCR | 2/17/2014 |- | proletaryo | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | bgaltman | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 53c9fe8baa4f96bafa6ef8a66af40557c5727d0a 10162 10161 2014-06-30T06:21:18Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (ground, Underpass = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.) 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 48f7f0aaa1b7ed7c5bcb32a0e52fb879aaf32216 10163 10162 2014-07-14T03:44:51Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Landmarks and Gas Stations'''; Waze currently doesn't have POIs (Places Of Interests) yet and instead use Landmarks and FourSquare as POI locators. When adding a Landmark or a Gas Station, make sure their location is properly identified through the add landmark draw function and add the address in the details as well. If a landmark will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 2ef707e6968dd712cd8b7564783565dd04127848 10164 10163 2014-07-14T03:55:52Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] ac729c67cc84425dbc37146aacfbe54f83191a1a 10165 10164 2014-07-14T03:56:49Z Kazmuth 35 /* Update Request (UR) closing policy */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">20k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits or level 4 **Countrywide - CM only *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 591bba36b350211a5e2e6e4b9b012126f772108c 10166 10165 2014-08-08T05:57:18Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 9b21a5c84d2f04d4da2635b10d19a1fd8d8a9ae0 10167 10166 2014-09-03T06:17:20Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Expressways and Toll Roads *'''Major Highway''' – Roads that crosses multiple provinces *'''Minor Highway''' – Roads that crosses multiple cities or municipalities *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] a71de9413e48a67406beb393b15e761101e2950a 10168 10167 2014-10-04T07:55:18Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads *'''Minor Highway''' – DPWH Secondary Roads *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the name leave it alone. Somebody else could edit it. It will be highlighted in red so that other editors can easily see it as an un-named street. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 20c538e049e76c080101414d658c068af5040e5b 10169 10168 2014-10-06T02:01:11Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads *'''Minor Highway''' – DPWH Secondary Roads *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 29ec28a5f04ab09d1cbab35f4f6e68730956635d 10170 10169 2014-10-10T13:29:06Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] d1f4b4614512091c151af28c4377be5124169907 10171 10170 2014-10-12T01:55:36Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be approved and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 8b4aed5f787b925ffe2f80fcc57a82af18e97499 10172 10171 2014-10-12T01:57:47Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be approved and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] def29bcd93ce442246d819edd7ee10c0dd51593a 0 1 10058 10057 2014-03-11T08:16:13Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''Complete Guide to Waze in the Philippines'''</big> (Under Development) Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Editing Resources for the Philippines]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philipines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - After reading the editing manual as well as the Philippine Map Editing Guide, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] ce422b53e0625ac67659236198a7c26fbf695ecf 10060 10059 2014-08-19T08:44:00Z Kazmuth 35 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - After reading the editing manual as well as the Philippine Map Editing Guide, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] cba5dfbe177a4fe0177294a6516abe4b2fd9bb4f 0 2 10173 10172 2014-10-12T02:02:25Z Kazmuth 35 /* Philippine Places Policy */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type might be going away soon so refrain from using it, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] ca8f1e5916ae3d939bad7c4a3e4c4670df6dc4cc 10174 10173 2014-10-12T04:21:14Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the minimum requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as an Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] f403f491578f09718f50709bdc9e93bf70b2cc5a 10175 10174 2014-10-20T05:36:17Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 0ab79932501ccaf5f00132851ee85f9b6174313a 10176 10175 2015-01-07T07:21:39Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 425c7df328b9d0ca2845568f2899a47befd41e2f 10177 10176 2015-01-08T09:54:27Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 8b467d11458cdfe150945c19b71847e633117580 10178 10177 2015-01-27T05:24:08Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues; 1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save. 2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save. 3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save. 4. Incorrect street direction - set the direction based on average or latest drives, select solved and save. 5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and '''don't''' mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 3a495142a86bed5eb82306e2e6ed7f1396f39f1d 10179 10178 2015-01-27T05:57:27Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details. For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details. Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details. Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue. "Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked. "Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map. "Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road. Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead. "Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed. "Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 195154746dc87efcca94cd2b1385de1ce595aa67 10180 10179 2015-01-27T06:00:08Z Kazmuth 35 /* Guidelines for Resolving Update Requests (UR) */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 7b89eedcb286edec8716ad0ec7f183c4e723fb33 10181 10180 2015-02-18T12:04:24Z Kazmuth 35 /* Update Request (UR) closing policy */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] eeca3bd3cde2897a1a9cd0ed29e52112f525a8de 10182 10181 2015-02-18T12:13:37Z Kazmuth 35 /* Update Request (UR) closing policy */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | zy_pher | NCR | 1/11/2014 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | zy_pher | Pangasinan | 7/12/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | Grand_Master_Jedi | Central Visayas (Region VII) | 4/26/2014 |- | Grand_Master_Jedi | Visayas Island Group | 5/16/2014 |- | zy_pher | Luzon Island Group | 5/16/2014 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 7c2bbf60a2aa7ad105c379bf90f08759fbb9adc1 10183 10182 2015-02-22T07:26:54Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | RangeRoverHSE | Eastern Visayas (Region VIII) | 1/27/2014 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | RangeRoverHSE | NCR | 1/11/2014 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 11/2/2014 |- | Adabadada | Eastern Visayas (Region VIII) | 11/2/2014 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] a61b878c75b8cdac18d959826c89df2d9a33caaa 10184 10183 2015-02-22T07:41:34Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 11/2/2014 |- | Adabadada | Eastern Visayas (Region VIII) | 11/2/2014 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 9cc98626bb2ea102c657bbd04351c499bd748175 10185 10184 2015-02-22T08:02:25Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | RenzDeion | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 8f506d38ab2468effec3f7d1a1a2570a9bde7e02 10186 10185 2015-02-22T11:58:21Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 6/29/2013 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] f11f42ded66707ef8e953143947b417323e9b58e 10187 10186 2015-02-22T12:35:25Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | deadlockprocess | Bacolod, Silay | 2/17/2014 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | deadlockprocess | Kabankalan, Ilog | 2/17/2014 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | deadlockprocess | CALABARZON (Region IV-A) | 2/17/2014 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | deadlockprocess | Iloilo City | 2/17/2014 |- | deadlockprocess | Iloilo Province | 3/3/2014 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | deadlockprocess | NCR | 2/17/2014 |- | deadlockprocess | Negros Occidental Province | 3/3/2014 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | deadlockprocess | Central Luzon (Region III) | 4/20/2014 |- | deadlockprocess | Central Visayas (Region VII) | 4/20/2014 |- | deadlockprocess | Western Visayas (Region VI) | 4/20/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | deadlockprocess | Mindanao Island Ground | 6/2/2014 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] b7dbdf8c2644dfd2fcc9fdfe350177ade3f0af96 10188 10187 2015-02-24T03:01:21Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 3a60a5313bcbbdb1a6ad624bb6fe32b6cefdace0 10189 10188 2015-07-11T00:37:40Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. If the street name has a N, E, W, and S initial and it does not refer to a cardinal direction, add a dot '.' to prevent Waze from reading it as such. 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] fcebf195126fd151f35a83da853f4a17f91c60a3 10190 10189 2015-08-04T08:09:09Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. If there are local (LGU) or other name for the street, add them as an alternative name :3. Use punctuation for initials except for cardinal directions :4. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :5. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :6. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :7. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :8. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] a766a08add3cf68b038dcfaa8fe3312fddb43dd4 10191 10190 2015-08-04T08:15:13Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. If there are local (LGU) or other name for the street, add them as an alternative name :3. Use punctuation for initials except for cardinal directions :4. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :5. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :6. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :7. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :8. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 7e8d4cfa0f2dfdae1cf15c28735f2b32bbc58cc7 10192 10191 2015-10-12T09:07:13Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not user multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] b71c7a3e7d69d13a00cafab6b3a48d485923075b 10193 10192 2015-10-12T09:07:47Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] a02e5467001f4dd608527c57e0626741bfaa056b 10194 10193 2015-12-10T12:41:50Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. == Philippine Places Policy == '''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; [https://wiki.waze.com/wiki/Places Places Wiki] '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (in the PH FB group). This means all Waze editors will remain at Level 1 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level (2) until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] fe28b73e50b35c6a96afd513d9d93439aa51007f 10195 10194 2015-12-28T03:04:32Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (in the PH FB group). This means all Waze editors will remain at Level 1 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level (2) until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs&nbsp;:) *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 5ea6f690aba5f5baffd65aa4f87851b8bd2dd7a8 10196 10195 2016-01-06T09:11:03Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Connect or create junctions (attach to existing roads) 6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 9. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 10. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 11.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 12. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will remain at Level 1 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 45d10359a352699ca04c41f7e630016b0546b4ec 10197 10196 2016-01-14T02:09:58Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets || 30 || 30 |- | Private Roads || Depends on traffic regulations of the area || Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will remain at Level 1 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 8e7aa439bd824591ba9e068f14b99169c08efab0 0 1 10061 10060 2015-01-27T05:17:31Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] d49b482b0096b791ac4a7408ce1ca24a9dce04ca 10062 10061 2015-01-27T05:26:58Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] c48d78a9d2584296443f8987aa16aead82748def 10063 10062 2015-03-02T02:22:02Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[waze:About|About Waze]]== {{About Waze}} ==[[Getting Started]]== {{Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] 3c661165617c700604347177c29866e873bfdb22 1 2015-06-21T08:15:04Z MediaWiki default 0 wikitext text/x-wiki <strong>MediaWiki has been successfully installed.</strong> Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list] * [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] * [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language] 8e0aa2f2a7829587801db67d0424d9b447e09867 10067 10066 2015-08-04T02:39:53Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as noteable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] [[Category:Philippines]] fccf7fd79549735a179dce3bd79eee90878b7d0a 10069 10068 2015-11-09T01:45:13Z Rccoros 5 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] bc38d1e0d0e9df8f7502b9618fe702ef5f6ec2e6 10070 10069 2015-12-28T03:10:41Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 11795ae305ffb6b5bfd2409f35a303ee09626869 10071 10070 2015-12-30T10:43:44Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer, if you are reading this then you probably want to learn more about how to use Waze or edit the map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place, read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 384fdc61ba5fcef3601f6c2761350d400e02ee31 0 3 10206 2015-03-02T02:14:38Z Kazmuth 35 Created page with "== Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. We first heard a..." wikitext text/x-wiki == Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. We first heard about the concept during the official Philippines Waze Meetup conducted June 2014. From there, we coordinated with Waze on the mechanics of the effort. Visit the [[MapRaid]] wiki for more details. Here are some of the stats from the MapRaids that were done on the Philippines {| class="wikitable sortable" |- ! Date !! Location !! # of Raiders !! Segments Handled !! Segments Created !! MPs Resolved !! URs Resolved !! PUs Handled !! Prev. Connectivity !! Pres. Connectivity |- | Sept 2014 || Metro Manila || 10 || 3104 || 877 || 8 || 255 || 577 || 95.05% || 95.213% |- | Oct 2014 || Central Luzon || 14 || 136619 || 46810 || 772 || 3290 || 9529 || || |- | Nov 2014 || Cavite and Laguna || 14 || 25702 || 8492 || 35 || 209 || 4200 || || |- | Feb 2015 || Metro Manila || 16 || 26930 || 5396 || 0 || 3070 || 6411 || 93.6% || 95.5% |} e7afeb766e44361978f15505dcfb29f32dad1927 10207 10206 2015-03-03T06:13:11Z Kazmuth 35 wikitext text/x-wiki == Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. We first heard about the concept during the official Philippines Waze Meetup conducted June 2014. From there, we coordinated with Waze on the mechanics of the effort. Visit the [[MapRaid]] wiki for more details. Here are some of the stats from the MapRaids that were done on the Philippines {| class="wikitable sortable" |- ! Date !! Location !! # of Raiders !! Segments Handled !! Segments Created !! MPs Resolved !! URs Resolved !! PUs Handled |- | Sept 2014 || Metro Manila || 10 || 3104 || 877 || 8 || 255 || 577 |- | Oct 2014 || Central Luzon || 14 || 136619 || 46810 || 772 || 3290 || 9529 |- | Nov 2014 || Cavite and Laguna || 14 || 25702 || 8492 || 35 || 209 || 4200 |- | Feb 2015 || Metro Manila || 16 || 26930 || 5396 || 0 || 3070 || 6411 |} 643811eeeedc63e7926c71e1ae3bb68d4d5604b9 10208 10207 2015-12-28T03:06:56Z Kazmuth 35 wikitext text/x-wiki == Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. We first heard about the concept during the official Philippines Waze Meetup conducted June 2014. From there, we coordinated with Waze on the mechanics of the effort. Visit the [[MapRaid]] wiki for more details. Here are some of the stats from the MapRaids that were done on the Philippines {| class="wikitable sortable" |- ! Date !! Location !! # of Raiders !! Segments Handled !! Segments Created !! MPs Resolved !! URs Resolved !! PUs Handled |- | Sept 2014 || Metro Manila || 10 || 3104 || 877 || 8 || 255 || 577 |- | Oct 2014 || Central Luzon || 14 || 136619 || 46810 || 772 || 3290 || 9529 |- | Nov 2014 || Cavite and Laguna || 14 || 25702 || 8492 || 35 || 209 || 4200 |- | Feb 2015 || Metro Manila || 16 || 26930 || 5396 || 0 || 3070 || 6411 |} [[Category:Philippines]] 80106a92c3cea95be509e73c29dbf3c9ee046175 0 4 10211 2015-12-28T02:59:30Z Kazmuth 35 Created page with "__TOC__ == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to..." wikitext text/x-wiki __TOC__ == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. 94216a169dcf17f7876c9e341a8b8f04e3bbd49b 10212 10211 2015-12-28T03:06:17Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. [[Category:Philippines]] 1563dac73b6c179aef44f8175f990103ed499789 0 5 10214 2015-12-28T03:00:59Z Kazmuth 35 Created page with "__TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM..." wikitext text/x-wiki __TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. 04f738e82bc61e0c4f5b474c92138e31258195d5 10215 10214 2015-12-28T03:05:55Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4. *Makati *Pasig *Caloocan *Las Pinas *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs. '''Primary Streets'''&nbsp;- should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. [[Category:Philippines]] ecb2939944eabb68a8c1a7c01dc9b3f4ad8d8f6d 10216 10215 2016-01-13T02:29:07Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already is almost complete and accurate. If an area is already considered complete, they may be locked to Level 5 for Freeway/Major/Minor Highways, Level 4 for Primary roads, and L3 for everything else. The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Primary Streets'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Landmarks''' There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations. *'''What not to lock''' Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. [[Category:Philippines]] 2646c9f92d2395336eff248175201e82160ad1eb 0 6 10221 2015-12-28T03:03:42Z Kazmuth 35 Created page with "__TOC__ == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an..." wikitext text/x-wiki __TOC__ == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' 48777d4f10aaf50d3b24e616ddecb559b3279e6c 10222 10221 2015-12-28T03:04:47Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] bcd757c5bf9f38096d45363cb0e9ffdef2913b08 10223 10222 2015-12-29T13:25:16Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippines Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. Champs are the community leaders Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. A Coordinator’s main responsibilities: Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. Global Champ and Coordinator kazmuth SpeedDzel Country Manager Baldugaras rider111 zy_pher - Luzon Division Manager Lu_Wei_Jie - Visayas Division Manager deadlockprocess - Mindanao Division Manager iPhone expert deadlockprocess shogsbro Android expert zy_pher Guardian4ngel shogsbro WME Editing expert zy_pher Guardian4ngel deadlockprocess shogsbro WME Beta Editor expert kazmuth Baldugaras Navigation / Routing expert deadlockprocess Sshogsbro Social Media expert zy_pher Guardian4ngel Dominatrix Localization expert kazmuth Local Champs iceden Ungas zy_pher Guardian4ngel deadlockprocess shogsbro Baldugaras Adabadada Lu_Wei_Jie Wiki Masters rccoros kazmuth == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 13f5db64efd93e8fc4d4366d9bf549755a9fb0e8 10224 10223 2015-12-29T13:32:18Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippines Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. Global Champ and Coordinator * kazmuth * SpeedDzel Country Manager * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager iPhone expert * deadlockprocess * shogsbro Android expert * zy_pher * Guardian4ngel * shogsbro WME Editing expert * zy_pher * Guardian4ngel * deadlockprocess * shogsbro WME Beta Editor expert * kazmuth * Baldugaras Navigation / Routing expert * deadlockprocess * shogsbro Social Media expert * zy_pher * Guardian4ngel * Dominatrix Localization expert * kazmuth Local Champs * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie Wiki Masters * rccoros * kazmuth == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 4adb397e045d5905516acad1ba3ef5ffc3f86ba8 10225 10224 2015-12-29T14:18:05Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. Global Champ and Coordinator * kazmuth * SpeedDzel Country Manager * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager iPhone expert * deadlockprocess * shogsbro Android expert * zy_pher * Guardian4ngel * shogsbro WME Editing expert * zy_pher * Guardian4ngel * deadlockprocess * shogsbro WME Beta Editor expert * kazmuth * Baldugaras Navigation / Routing expert * deadlockprocess * shogsbro Social Media expert * zy_pher * Guardian4ngel * Dominatrix Localization expert * kazmuth Local Champs * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie Wiki Masters * rccoros * kazmuth == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | kid_ant | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_32m24hzt | Cebu City | 7/26/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | foruboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 34e4460bfb358eafa6e4d6b7ab4995c846d2ea93 10226 10225 2016-01-13T01:59:52Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. Global Champ and Coordinator * kazmuth * SpeedDzel Country Manager * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager iPhone expert * deadlockprocess * shogsbro Android expert * zy_pher * Guardian4ngel * shogsbro WME Editing expert * zy_pher * Guardian4ngel * deadlockprocess * shogsbro WME Beta Editor expert * kazmuth * Baldugaras Navigation / Routing expert * deadlockprocess * shogsbro Social Media expert * zy_pher * Guardian4ngel * Dominatrix Localization expert * kazmuth Local Champs * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie Wiki Masters * rccoros * kazmuth == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | roseAntonio | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | furuboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] fa3d3b0c4de048cc3ee0e0073e4404bc2422c7ad 10227 10226 2016-01-13T02:10:25Z Kazmuth 35 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. Global Champ and Coordinator * kazmuth * SpeedDzel Country Manager * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager iPhone expert * deadlockprocess * shogsbro Android expert * zy_pher * Guardian4ngel * shogsbro WME Editing expert * zy_pher * Guardian4ngel * deadlockprocess * shogsbro WME Beta Editor expert * kazmuth * Baldugaras Navigation / Routing expert * deadlockprocess * shogsbro Social Media expert * zy_pher * Guardian4ngel * Dominatrix Localization expert * kazmuth Local Champs * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie Wiki Masters * rccoros * kazmuth == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | roseAntonio | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | furuboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] b75eec68e5da43e3c2df0b4bca96843b723606c6 0 7 10229 2015-12-30T10:48:04Z Kazmuth 35 Created page with "__TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissi..." wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; Places Wiki *'''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing *'''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images *'''Updates on Places' Information''' The general guideline to use to determine whether to Accept the update is, ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long (expand thumbnail to the right). Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. [[Category:Philippines]] 0e32b9d739e16e1cefb0669fe831995c756ca723 10230 10229 2015-12-30T10:49:00Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; Places Wiki '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information''' The general guideline to use to determine whether to Accept the update is, ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long (expand thumbnail to the right). Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. [[Category:Philippines]] 3b63074264b0757da2d2a4dccf26b1c3ad034ca4 0 2 10198 10197 2016-01-14T02:11:29Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets || 30 || 30 |- | Private/PL Roads || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will remain at Level 1 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] ac376ecaae2772c979ae7b9415b725eff7717f83 10199 10198 2016-01-16T15:09:53Z Kazmuth 35 /* Other Questions and Tips for the Pinoy Waze Editor */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets || 30 || 30 |- | Private/PL Roads || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 242d9540cca97e568125e36717926e8b6f105b78 10200 10199 2016-01-28T01:43:16Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Service Roads''' – '''This type has been deprecated, use Street type instead.''' usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways) *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. You can also select Walking Trails if the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets || 30 || 30 |- | Private/PL Roads || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [http://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 5daf416db33db820f582546ca1f3efa68d3b3e4a 10201 10200 2016-02-09T08:01:02Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets || 30 || 30 |- | Private/PL Roads || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 0ea220d229d294bbe26a7d24e0719836be41a1f5 10202 10201 2016-02-23T02:03:57Z Shogsbro 40 Add 20kph speed for roads with sleeping policemen wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets, except those with sleeping policemen || 30 || 30 |- | Private & Parking Lot roads, Streets with sleeping policemen || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 0f11e23741372e0f18a2e9a65da2e63379cf0b47 10203 10202 2016-02-28T09:43:35Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets, except those with sleeping policemen || 30 || 30 |- | Private & Parking Lot roads, Streets with sleeping policemen || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] aa329d08c690ddf5f3f8a6bb9974f79f96731351 10204 10203 2016-03-09T09:23:20Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets, except those with speedbumps (humps) || 30 || 30 |- | Private & Parking Lot roads, Streets with speedbumps (humps) || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 35cbb93d42b9caab3db26705c01a01f09eda288b 10205 10204 2016-05-09T19:53:04Z Wottem 25 131 revisions imported wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; *'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid *'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population *'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *'''Street '''– ordinary street, mainly residential *'''Dirt-roads / 4x4 Trails''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. *'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets, except those with speedbumps (humps) || 30 || 30 |- | Private & Parking Lot roads, Streets with speedbumps (humps) || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 35cbb93d42b9caab3db26705c01a01f09eda288b 10314 10205 2017-04-27T03:27:44Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; #**'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid #**'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population #**'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. #**'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels #**'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads #**'''Street '''– ordinary street, mainly residential #**'''Off-road / Not maintained''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. #**'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. #**'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. #**'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set directionality (two way or one way) 4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 5. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets, except those with speedbumps (humps) || 30 || 30 |- | Private & Parking Lot roads, Streets with speedbumps (humps) || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} 6. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 7. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 8. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 5a6f1749c3a67b13c0a17769d9c8d686c5303110 10315 10314 2017-04-27T03:28:49Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; #**'''Freeways '''– Toll Roads or Expressways where a toll fee needs to be paid #**'''Major Highway''' – DPWH Primary Roads or roads that connect cities of > 100,000 population #**'''Minor Highway''' – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. #**'''Ramps '''– On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels #**'''Primary Street''' – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads #**'''Street '''– ordinary street, mainly residential #**'''Off-road / Not maintained''' – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. #**'''Parking Lot Road''' – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, '''DO NOT''' map all the lanes inside the parking area. #**'''Private Road''' – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. #**'''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', '''Runway/Taxiway''' – other non drivable and non-routable roads, '''do not map these''' unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets, except those with speedbumps (humps) || 30 || 30 |- | Private & Parking Lot roads, Streets with speedbumps (humps) || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] f3308d31bced3108137bf37fa2e5e7d1136bfb53 10316 10315 2017-04-27T03:29:30Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads || 40 || 40 |- | Streets, except those with speedbumps (humps) || 30 || 30 |- | Private & Parking Lot roads, Streets with speedbumps (humps) || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing 9. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 10. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 11. When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. 12.'''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] f05e232699adb52fb0d172d9b69a3847326b1648 10317 10316 2017-04-27T03:31:10Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - :1. Always use the official name as the street name (DPWH Name) :2. Do not use multiple street names separated with a slash "/" :3. If there are local (LGU) or other name for the street, add them as an alternative name :4. Use punctuation for initials except for cardinal directions :5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions :6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) :7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name :8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' :9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the<span style="color:#ff0000;">&nbsp;AREA</span>''''',&nbsp;'''''<span style="color:#ff0000;">SUBDIVISION</span>, <span style="color:#ff0000;">DISTRICT&nbsp;</span>or <span style="color:#ff0000;">BARANGAY </span>NAME nor should it be combined with the <span style="color:#ff0000;">PROVINCIAL&nbsp;</span>Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label&nbsp;(equivalent to State) activated. For the time being, to address this issue, the &nbsp;province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: *There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. *GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. *There are a lot of roads intersecting which can only turn onto the nearest direction of travel. *Google Maps or other mapping source show it as a split road *The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Places_Policy Places Policy] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 3e1be9a059a6f824b027c4d3e1d81824529aee3b 10318 10317 2017-04-27T03:32:33Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki __TOC__ == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == Other Questions and Tips for the Pinoy Waze Editor == Here are the most asked questions from Pinoy Waze Editors *'''Is there a manual for Waze map editing?''' There is a [[Waze Map Editor]] that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. *'''Why am I not leveling up to Level 2 or 3?''' We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]). This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] *'''How do I apply to be an Area Manager?''' To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] *'''How long does it take until my edits gets displayed on my waze client?''' It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area *'''When I encounter traffic on the road, what type do I report?''' You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph *'''I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?''' The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them *'''What is the difference between Map Issues and Update Requests?''' Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. *'''How do I fix Map Issues?''' Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. *'''How do I fix Update Requests?''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. *'''Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?''' On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. *'''Waze does not use the U-Turn segment I created between two roads, what could be the problem?''' Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. *'''Are there any shortcut keys for the Waze Map Editor?''' You can view the wiki page on [[Keyboard shortcuts]] *'''Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?''' Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. *'''I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?''' You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. *'''The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?''' The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. *'''There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?''' You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. *'''Search function doesn't work, how do I fix it?''' This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. *'''I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?''' If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). *'''How do I report flooding so that wazers will not be routed on a flooded road?''' Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country. *The road will be opened when a number of users drive through the road. [[Category:Philippines]] 646a23e04cb7cfa38d99fd388f952865e2485d94 10319 10318 2017-04-27T03:33:05Z Kazmuth 35 wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 46f3abe9d75bd31f4998b3c1cfce0a808bcbd3b9 10320 10319 2017-04-27T03:46:27Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; #* Freeways – Toll Roads or Expressways where a toll fee needs to be paid #* Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels #* Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population #* Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. #* Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads #* Street – ordinary street, mainly residential #* Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. #* Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. #* Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. #* Ferry - Ferries that meet any of these conditions should generally not be mapped #*** Passenger ferries without vehicles #*** Ferries requiring pre-booking #*** Private ferries unavailable to the general public #*** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map #* Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. # Set road type attributes. #* Toll Road - Expressways where toll fees are collected #* Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through #* Tunnel - If the road is underground # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. #* # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 5d80503348e3c413e97b2ff6eb18f4e4bc81fe28 10321 10320 2017-04-27T04:16:09Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; #* Freeways – Toll Roads or Expressways where a toll fee needs to be paid #* Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels #* Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population #* Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. #* Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads #* Street – ordinary street, mainly residential #* Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. #* Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. #* Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. #* Ferry - Ferries that meet any of these conditions should generally not be mapped #*** Passenger ferries without vehicles #*** Ferries requiring pre-booking #*** Private ferries unavailable to the general public #*** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map #* Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. # Set road type attributes. #* Toll Road - Expressways where toll fees are collected #* Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through #* Tunnel - If the road is underground # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. {| class="wikitable" !Maximum allowed speed in KPH !Cars and Motorcycles !Trucks and Buses |- |Expressways |100 |80 |- |Major Highways |80 |60 |- |Minor Highways |60 |60 |- |Primary Roads, On/Off Ramps |40 |40 |- |Private & Parking Lot roads, Streets with speedbumps (humps) |20 / Depends on traffic regulations of the area |20 / Depends on traffic regulations of the area |- |Streets, except those with speedbumps (humps) |30 |30 |} # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] d295f984b907d954045b62f273d5e7191f265889 10323 10321 2017-05-14T11:21:39Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; #* Freeways – Toll Roads or Expressways where a toll fee needs to be paid #* Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels #* Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population #* Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. #* Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads #* Street – ordinary street, mainly residential #* Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. #* Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. #* Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. #* Ferry - Ferries that meet any of these conditions should generally not be mapped #*** Passenger ferries without vehicles #*** Ferries requiring pre-booking #*** Private ferries unavailable to the general public #*** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map #* Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. # Set road type attributes. #* Toll Road - Expressways where toll fees are collected #* Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through #* Tunnel - If the road is underground # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 158800ba9fde3b62a98dd7c2539ea60a9e39f04c 10326 10323 2017-05-14T11:45:50Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; #* Freeways – Toll Roads or Expressways where a toll fee needs to be paid #* Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels #* Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population #* Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. #* Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads #* Street – ordinary street, mainly residential #* Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. #* Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. #* Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. #* Ferry - Ferries that meet any of these conditions should generally not be mapped #*** Passenger ferries without vehicles #*** Ferries requiring pre-booking #*** Private ferries unavailable to the general public #*** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map #* Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. # Set road type attributes. #* Toll Road - Expressways where toll fees are collected #* Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through #* Tunnel - If the road is underground # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. ## Always use the official name as the street name (DPWH Name) ## Do not use multiple street names separated with a slash "/" ## If there are local (LGU) or other name for the street, add them as an alternative name ## Use punctuation for initials except for cardinal directions ## N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions ## Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) ## Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name ## Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' ## Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: #* There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. #* GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. #* U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: #* There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. #* There are a lot of roads intersecting which can only turn onto the nearest direction of travel. #* Google Maps or other mapping source show it as a split road #* The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: #* When the turn lane physically separates from the main road well in advance of the intersection #* When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation #* When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier #* When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector #* When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane #* When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. #: '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. #: '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [[Philippines/Places Policy |Places Policy]] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 8fc8ce50962ebc3957e0ece9b30b79ffd8abf332 10327 10326 2017-05-14T12:02:07Z Kazmuth 35 wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; #* Freeways – Toll Roads or Expressways where a toll fee needs to be paid #* Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels #* Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population #* Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. #* Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads #* Street – ordinary street, mainly residential #* Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. #* Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. #* Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. #* Ferry - Ferries that meet any of these conditions should generally not be mapped #*** Passenger ferries without vehicles #*** Ferries requiring pre-booking #*** Private ferries unavailable to the general public #*** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map #* Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. # Set road type attributes. #* Toll Road - Expressways where toll fees are collected #* Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through #* Tunnel - If the road is underground # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. ## Always use the official name as the street name (DPWH Name) ## Do not use multiple street names separated with a slash "/" ## If there are local (LGU) or other name for the street, add them as an alternative name ## Use punctuation for initials except for cardinal directions ## N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions ## Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) ## Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name ## Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' ## Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: #* There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. #* GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. #* U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: #* There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. #* There are a lot of roads intersecting which can only turn onto the nearest direction of travel. #* Google Maps or other mapping source show it as a split road #* The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: #* When the turn lane physically separates from the main road well in advance of the intersection #* When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation #* When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier #* When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector #* When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane #* When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. ##: '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. ##: '''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [[Philippines/Places Policy |Places Policy]] for more details on what can be added. '''DO NOT MAP MILITARY INSTALLATIONS OR BASES''' # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 34d9e7fbf2adaab7697d134e7d0e8405802442f7 10328 10327 2017-05-14T12:02:50Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; #* Freeways – Toll Roads or Expressways where a toll fee needs to be paid #* Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels #* Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population #* Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. #* Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads #* Street – ordinary street, mainly residential #* Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. #* Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. #* Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. #* Ferry - Ferries that meet any of these conditions should generally not be mapped #*** Passenger ferries without vehicles #*** Ferries requiring pre-booking #*** Private ferries unavailable to the general public #*** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map #* Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. # Set road type attributes. #* Toll Road - Expressways where toll fees are collected #* Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through #* Tunnel - If the road is underground # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. ## Always use the official name as the street name (DPWH Name) ## Do not use multiple street names separated with a slash "/" ## If there are local (LGU) or other name for the street, add them as an alternative name ## Use punctuation for initials except for cardinal directions ## N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions ## Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) ## Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name ## Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' ## Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road ''should''' be split if: #* There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. #* GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. #* U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: #* There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. #* There are a lot of roads intersecting which can only turn onto the nearest direction of travel. #* Google Maps or other mapping source show it as a split road #* The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: #* When the turn lane physically separates from the main road well in advance of the intersection #* When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation #* When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier #* When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector #* When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane #* When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Area Places, Point Places, and Gas Stations'''; When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are; '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 0cdb7e319f7167e09f675b669a20a9b6138ee7d6 10329 10328 2017-05-14T12:21:34Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. # Create road (whether tracing aerial images/gps points, or from recorded drives) # Set road type, some suggestions; #* Freeways – Toll Roads or Expressways where a toll fee needs to be paid #* Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels #* Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population #* Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. #* Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads #* Street – ordinary street, mainly residential #* Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. #* Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. #* Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. #* Ferry - Ferries that meet any of these conditions should generally not be mapped #*** Passenger ferries without vehicles #*** Ferries requiring pre-booking #*** Private ferries unavailable to the general public #*** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map #* Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. # Set road type attributes. #* Toll Road - Expressways where toll fees are collected #* Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through #* Tunnel - If the road is underground # Set directionality (two way or one way) # Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. # Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. # Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' # Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. # Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. ## Always use the official name as the street name (DPWH Name) ## Do not use multiple street names separated with a slash "/" ## If there are local (LGU) or other name for the street, add them as an alternative name ## Use punctuation for initials except for cardinal directions ## N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions ## Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) ## Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name ## Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' ## Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> # When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Please give extra care on labeling the '''City''' of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made. Kindly stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. # '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road should be split if: #* There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. #* GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. #* U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: #* There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. #* There are a lot of roads intersecting which can only turn onto the nearest direction of travel. #* Google Maps or other mapping source show it as a split road #* The non-drivable median is interrupted by a cross segment at most intersections. #* '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: #* When the turn lane physically separates from the main road well in advance of the intersection #* When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation #* When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier #* When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector #* When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane #* When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc # When you are confident on an area you have mapped,'''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Phillipine Locking Policy] for more details. # '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. #* '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. #* '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. # '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 2dfac3dcedbcb01743adb4db6cd9e6efba5097e4 10330 10329 2017-05-14T12:35:07Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads\ * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set road type attributes. * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [https://wiki.waze.com/wiki/Philippines/Locking Philippines Locking Policy] for more details. 12. '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 3f28db82476897948a424883d9dcd5d5fcb4c180 0 7 10231 10230 2016-01-23T10:16:26Z Kazmuth 35 /* Philippine Places Policy */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; Places Wiki '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information''' The general guideline to use to determine whether to Accept the update is, ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. [[Category:Philippines]] 582e928078623603243f0a43c555d2b9112379dc 10232 10231 2016-01-27T03:34:06Z Kazmuth 35 /* Philippine Places Policy */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; Places Wiki '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information''' The general guideline to use to determine whether to Accept the update is, ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. [[Category:Philippines]] 6340aac1e0d80b33a3181aaaa5750c0fed04793b 10233 10232 2016-01-28T01:47:44Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). '''New Places'''<br /> When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are;<br /> :'''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''Approve''' *New places that meet the criteria. '''Reject'''<br /> *New places that do not meet the criteria. <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; Places Wiki '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information''' The general guideline to use to determine whether to Accept the update is, ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to residential if the place is not a house [[Category:Philippines]] 784e7d42323c9217f49b22116cdd6ca2f1d6761c 10234 10233 2016-01-28T01:50:43Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). '''New Places'''<br /> When adding Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are;<br /> :'''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''Approve''' *New places that meet the criteria. '''Reject'''<br /> *New places that do not meet the criteria. <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; Places Wiki '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to residential if the place is not a house [[Category:Philippines]] 9bf81e934b4e37edb16ba4b25281e7d16843612e 10235 10234 2016-01-28T01:52:55Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature). '''New Places'''<br /> When adding new Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. Also make sure that it is not a duplicate of an already existing place, either an area place or a point place. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are;<br /> :'''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''Approve''' *New places that meet the criteria. '''Reject'''<br /> *New places that do not meet the criteria. <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted. Refer to this link for more details; Places Wiki '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to residential if the place is not a house [[Category:Philippines]] 778d7c5284d9b07010533796450e54b6efbfc7a1 10236 10235 2016-01-31T11:02:37Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. '''New Places'''<br /> When adding new Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. Also make sure that it is not a duplicate of an already existing place, either an area place or a point place. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are;<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues'''. So if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''Approve''' *New places that meet the criteria. '''Reject'''<br /> *New places that do not meet the criteria. <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to residential if the place is not a house [[Category:Philippines]] 4f828778e3120619d15a474a6157526ea71e0d2e 10237 10236 2016-02-22T14:08:12Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. '''New Places'''<br /> When adding new Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. Also make sure that it is not a duplicate of an already existing place, either an area place or a point place. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are;<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues'''. So if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''Approve''' *New places that meet the criteria. '''Reject'''<br /> *New places that do not meet the criteria. <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, ''"Adding place addresses"'' When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to residential if the place is not a house [[Category:Philippines]] 8d90ee8ef63bf2f2ceef71a4a5d1437506ab1084 10238 10237 2016-02-22T14:09:38Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. '''New Places'''<br /> When adding new Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. Also make sure that it is not a duplicate of an already existing place, either an area place or a point place. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are;<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues'''. So if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''Approve''' *New places that meet the criteria. '''Reject'''<br /> *New places that do not meet the criteria. <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to residential if the place is not a house [[Category:Philippines]] 5cbe415ef1d258b2d3a1efe917b6110b74952107 10239 10238 2016-02-28T09:58:49Z Kazmuth 35 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. '''New Places'''<br /> When adding new Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. Also make sure that it is not a duplicate of an already existing place, either an area place or a point place. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are;<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues'''. So if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 60f7d1c57f30f98adf3354d00c2b02e3dbd5e8d6 10240 10239 2016-05-09T19:53:07Z Wottem 25 11 revisions imported wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. '''New Places'''<br /> When adding new Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. Also make sure that it is not a duplicate of an already existing place, either an area place or a point place. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are;<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues'''. So if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 60f7d1c57f30f98adf3354d00c2b02e3dbd5e8d6 0 3 10209 10208 2016-01-31T11:20:40Z Kazmuth 35 wikitext text/x-wiki == Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. We first heard about the concept during the official Philippines Waze Meetup conducted June 2014. From there, we coordinated with Waze on the mechanics of the effort. Visit the [[MapRaid]] wiki for more details. Here are some of the stats from the MapRaids that were done on the Philippines {| class="wikitable sortable" |- ! Date !! Location !! # of Raiders !! Segments Handled !! Segments Created !! MPs Resolved !! URs Resolved !! PUs Handled !! Previous Connectivity !! New Connectivity !! Change |- | Sept 2014 || Metro Manila || 10 || 3104 || 877 || 8 || 255 || 577 || 88.74% || 95.213% || 6.473% |- | Oct 2014 || Central Luzon || 14 || 136619 || 46810 || 772 || 3290 || 9529 || || || |- | Nov 2014 || Cavite and Laguna || 14 || 25702 || 8492 || 35 || 209 || 4200 || || || |- | Feb 2015 || Metro Manila || 16 || 26930 || 5396 || 0 || 3070 || 6411 || 93.6% || 95.5% || 1.9% |- | Dec 2015 || Metro CDO || 8 || 21324 || 8466 || 0 || 54 || 476 || 93.28% || 96.8% || 3.52% |- | Dec 2015 || Metro Cebu || 9 || 19653 || 6914 || 0 || 190 || 4363 || 97.72% || 98.4% || 0.68% |- | Dec 2015 || Metro Davao || 9 || 55917 || 23835 || 0 || 58 || 1921 || 96.94% || 97.7% || 0.76% |} [[Category:Philippines]] 9ac296bae6f301c53dc473f2a053ba12d52e018d 10210 10209 2016-05-09T19:53:05Z Wottem 25 4 revisions imported wikitext text/x-wiki == Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. We first heard about the concept during the official Philippines Waze Meetup conducted June 2014. From there, we coordinated with Waze on the mechanics of the effort. Visit the [[MapRaid]] wiki for more details. Here are some of the stats from the MapRaids that were done on the Philippines {| class="wikitable sortable" |- ! Date !! Location !! # of Raiders !! Segments Handled !! Segments Created !! MPs Resolved !! URs Resolved !! PUs Handled !! Previous Connectivity !! New Connectivity !! Change |- | Sept 2014 || Metro Manila || 10 || 3104 || 877 || 8 || 255 || 577 || 88.74% || 95.213% || 6.473% |- | Oct 2014 || Central Luzon || 14 || 136619 || 46810 || 772 || 3290 || 9529 || || || |- | Nov 2014 || Cavite and Laguna || 14 || 25702 || 8492 || 35 || 209 || 4200 || || || |- | Feb 2015 || Metro Manila || 16 || 26930 || 5396 || 0 || 3070 || 6411 || 93.6% || 95.5% || 1.9% |- | Dec 2015 || Metro CDO || 8 || 21324 || 8466 || 0 || 54 || 476 || 93.28% || 96.8% || 3.52% |- | Dec 2015 || Metro Cebu || 9 || 19653 || 6914 || 0 || 190 || 4363 || 97.72% || 98.4% || 0.68% |- | Dec 2015 || Metro Davao || 9 || 55917 || 23835 || 0 || 58 || 1921 || 96.94% || 97.7% || 0.76% |} [[Category:Philippines]] 9ac296bae6f301c53dc473f2a053ba12d52e018d 0 5 10217 10216 2016-02-12T10:29:38Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already is almost complete and accurate. If an area is already considered complete, they may be locked to Level 5 for Freeway/Major/Minor Highways, Level 4 for Primary roads, and L3 for everything else. The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Primary Streets'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively). '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Places''' All places will be locked to level 4 to prevent unnecessary edits. This will ensure that all edits will be approved by the local champs only. *'''What not to lock''' Unnamed roads and segment in NCR should be locked to level 2 and those outside NCR should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. [[Category:Philippines]] 7db98f24e02ff1ebd3795a5408f7fa96e52beac7 10218 10217 2016-02-12T10:39:30Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already is almost complete and accurate. If an area is already considered complete, they may be locked to Level 5 for Freeway/Major/Minor Highways, Level 4 for Primary roads, and L3 for everything else. The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Primary Streets'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' All named segments will be locked to level 3. '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Places''' All places will be locked to level 4 to prevent unnecessary edits. This will ensure that all edits will be approved by the local champs only. *'''What not to lock''' Unnamed roads and segment in NCR should be locked to level 2 and those outside NCR should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. [[Category:Philippines]] 146c5d41d68aa9ceadffcae3dc4fbda517878146 10219 10218 2016-02-23T02:03:11Z Shogsbro 40 Add Airports as L6 lock wikitext text/x-wiki __TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already is almost complete and accurate. If an area is already considered complete, they may be locked to Level 5 for Freeway/Major/Minor Highways, Level 4 for Primary roads, and L3 for everything else. The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Primary Streets'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Airports'''&nbsp;- should be locked at L6 to prevent accidental edit and deletion. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' All named segments will be locked to level 3. '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Places''' All places will be locked to level 4 to prevent unnecessary edits. This will ensure that all edits will be approved by the local champs only. *'''What not to lock''' Unnamed roads and segment in NCR should be locked to level 2 and those outside NCR should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. [[Category:Philippines]] 86d9b8fb2e45711c12ec7e0077e58e2e5f29d664 10220 10219 2016-05-09T19:53:05Z Wottem 25 6 revisions imported wikitext text/x-wiki __TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; *1. Already is almost complete and accurate. If an area is already considered complete, they may be locked to Level 5 for Freeway/Major/Minor Highways, Level 4 for Primary roads, and L3 for everything else. The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. *2. Changes or edits to these segments are seldom done or does not happen that often. *3. Segments that are high value roads where incorrect edits will result in routing issues. *4. Vandalism on the Waze maps *5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Primary Streets'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Airports'''&nbsp;- should be locked at L6 to prevent accidental edit and deletion. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' All named segments will be locked to level 3. '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Places''' All places will be locked to level 4 to prevent unnecessary edits. This will ensure that all edits will be approved by the local champs only. *'''What not to lock''' Unnamed roads and segment in NCR should be locked to level 2 and those outside NCR should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. [[Category:Philippines]] 86d9b8fb2e45711c12ec7e0077e58e2e5f29d664 0 1 10073 10072 2016-05-09T19:52:45Z Wottem 25 28 revisions imported wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 1f3424e386e25b5aee30b20fab8570e340c5c7d9 10312 10073 2016-05-12T20:46:42Z Wottem 25 Wottem העביר את הדף [[Philippines]] ל־[[Main Page]] wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 1f3424e386e25b5aee30b20fab8570e340c5c7d9 10322 10312 2017-05-14T11:18:58Z Kazmuth 35 /* Getting Started */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES (Note that this is for the USA but most are applicable to Waze Philippines as well) - https://wiki.waze.com/wiki/Edits_to_avoid_(USA) {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] f4908669640feece72f19fa2b2c386b5496f471b 10324 10322 2017-05-14T11:25:06Z Kazmuth 35 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES (Note that this is for the USA but most are applicable to Waze Philippines as well) - https://wiki.waze.com/wiki/Edits_to_avoid_(USA) {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 31f54626a720c9b989e8cde5d0d1a5d6ef8dd384 0 4 10213 10212 2016-05-09T19:53:05Z Wottem 25 2 revisions imported wikitext text/x-wiki __TOC__ == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the [https://wiki.waze.com/wiki/Editing_Resources_for_the_Philippines#Update_Request_.28UR.29_closing_policy Update Request closing policy] *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. [[Category:Philippines]] 1563dac73b6c179aef44f8175f990103ed499789 0 6 10228 10227 2016-05-09T19:53:06Z Wottem 25 7 revisions imported wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. Global Champ and Coordinator * kazmuth * SpeedDzel Country Manager * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager iPhone expert * deadlockprocess * shogsbro Android expert * zy_pher * Guardian4ngel * shogsbro WME Editing expert * zy_pher * Guardian4ngel * deadlockprocess * shogsbro WME Beta Editor expert * kazmuth * Baldugaras Navigation / Routing expert * deadlockprocess * shogsbro Social Media expert * zy_pher * Guardian4ngel * Dominatrix Localization expert * kazmuth Local Champs * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie Wiki Masters * rccoros * kazmuth == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | roseAntonio | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | furuboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] b75eec68e5da43e3c2df0b4bca96843b723606c6 0 8 10276 10275 2016-05-09T19:53:09Z Wottem 25 35 revisions imported wikitext text/x-wiki <!-- #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####----- #### This page has been curated #### #### to be included in the new #### #### Wazeopedia - GLOBAL Wiki. #### #### Please do not make any #### #### edits on this page without #### #### PRIOR CONSENSUS in the Wiki #### #### Updates and Discussions #### #### forum thread for this page. #### #### If a specific forum thread #### #### for this page doesn't exist #### #### please start one. #### #### www.waze.com/forum/ #### #### viewforum.php?f=276 #### #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--> * '''Read''' the topics on [http://support.google.com/waze Waze Help Center] * '''Get''' help when you have Waze running but the map shows few or no roads, or streets with no names, or you travel to an unmapped area * '''Understand''' the [[Timeline of updating process|timing of updates]], including when you can edit roads you have driven on * '''Edit''' ** ''Please do not'' edit the map until you have read the [[Waze Map Editor]] manual and reviewed the [[best map editing practice]]s * '''Use''' the [[Dashboard|My Dashboard section on the Waze website]] * '''Read''' the [[FAQ|answers to Frequently Asked Questions (FAQ)]] and the [[glossary]] of terms * '''Participate''' in the [[Discussion Forums|announcements and discussion forums]] '''If you have problems''', try and find your own solution or ask the community for help: * Use the Wiki - there is a search box just to the left * Use the [[Discussion Forums]] '''If all else fails''', you can [[email Waze with your problem]] a871b30fca7842639c622022abe719b4f8616da9 0 9 10307 10306 2016-05-09T19:53:11Z Wottem 25 30 revisions imported wikitext text/x-wiki <!-- This page is transcluded into the main page and possibly other pages -->Waze is a free navigation app for your GPS equipped smartphone. It has the following features: * Spoken turn-by-turn directions * Spoken street names (Text-to-Speech) {{ref label|a|a}} * Real time traffic reports * Real time Gas Prices {{ref label|b|b}} * Toll road avoidance {{ref label|b|b}} * Free regular updates to the map that [[improve and edit the maps| you can help make]] are installed automatically * Search for destinations how you like: entire address at once, category, place name, landmark or use the addresses from your contacts * Integrated destination search: Google, Foursquare, Bing * Support for apps to insert destinations into Waze, such as Localscope * Support for multiple [[Countries and Languages| languages]] * Gaming elements for fun and integrated [[social networking]] <small>{{note|a|a}} BETA: in selected countries<br/> {{note|b|b}} Toll Roads and Gas Prices dependent on user contribution</small> Read more about the amazing way Waze gets better when you [[just drive around with Waze turned on]] <noinclude><!-- prevents the pages receiving this page from picking up this category --> [[Category:Transcludable pages]] </noinclude> b2b110f051d39b6a93c89d2f3b95becff1ba9c60 10 10 10309 10308 2016-05-09T19:53:12Z Wottem 25 1 revision imported wikitext text/x-wiki <span class="citation wikicite" id="endnote_{{{1}}}"><b>[[#ref_{{{1}}}|^{{{2|}}}]]</b>{{#if:{{{3|}}}|&nbsp;{{{3|}}}}}</span> <noinclude> {{Documentation|Template:Ref/doc}} <!-- Add categories and interwikis to the /doc subpage, not here! --> </noinclude> 0b106806c7c057c175f8f5ca1e71538a40e045b2 10 11 10311 10310 2016-05-09T19:53:12Z Wottem 25 1 revision imported wikitext text/x-wiki <sup class="reference" {{#ifeq:{{{noid}}}|noid||id="ref_{{{1}}}{{{3|}}}"}}>[[#endnote_{{{1}}}{{{3|}}}|[{{{2}}}]]]</sup><noinclude> {{Documentation|Template:Ref/doc}} <!-- Add categories and interwikis to the /doc subpage, not here! --> </noinclude> c0b3dd908e57762a6aabdce479a3405613808656 0 12 10313 2016-05-12T20:46:43Z Wottem 25 Wottem העביר את הדף [[Philippines]] ל־[[Main Page]] wikitext text/x-wiki #REDIRECT [[Main Page]] c222ad63e9e6a1e286ff83e0861447ce17bf759f 0 13 10325 2017-05-14T11:30:40Z Kazmuth 35 Created page with "The speedlimits in the Philippines are stated on [http://www.gov.ph/1964/06/20/republic-act-no-4136/ REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as..." wikitext text/x-wiki The speedlimits in the Philippines are stated on [http://www.gov.ph/1964/06/20/republic-act-no-4136/ REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed'' and are as follows {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads, On/Off Ramps || 40 || 40 |- | Streets, except those with speedbumps (humps) || 30 || 30 |- | Private & Parking Lot roads, Streets with speedbumps (humps) || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} [[Category:Philippines]] 6c3c7c2df37a08f2d7c26a384cc76452b5d0480b 0 1 10331 10324 2017-05-14T12:36:05Z Kazmuth 35 /* Getting Started */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - https://wiki.waze.com/wiki/Edits_to_avoid_(USA) {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] a441e79207b6b6cf710eed75bf5b868e337da0b7 10332 10331 2017-05-14T12:41:35Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - https://wiki.waze.com/wiki/Edits_to_avoid_(USA) {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 508d9f0bfc8607b98099b852c50e1b04ea1194c4 10334 10332 2017-05-14T12:48:46Z Kazmuth 35 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 78dc08d5bbb8ada9e01e678a52682d9673eec356 10335 10334 2017-05-14T12:51:54Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Global/Best map editing practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 3da726522205cbee1ee1e1f8fdcaebaf1cc62321 10336 10335 2017-05-14T12:54:16Z Kazmuth 35 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Place Update Requests acceptable submissions * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] a5d2afffd53ec6ad4d1583fd0ff7161c05b5074f 10355 10336 2017-05-17T05:12:15Z Adabadada 39 /* Editing Resources for the Philippines */ Updated description for Places Policy wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the general standards and guides referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 834eed5af3d001c41d98617ebc408a7c5122c936 10372 10355 2017-05-17T18:38:42Z Adabadada 39 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete listing of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] d860fe07ce6c8b7c7591aa91aacd47f34a38a6c1 10373 10372 2017-05-17T18:41:11Z Adabadada 39 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Resources for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] e65499953845917fb8d6353400fc52904dc31384 10375 10373 2017-05-18T16:19:36Z Adabadada 39 /* Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Guidelines for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] a39aae306dd8e2ff6e6dfef80aea5cc68bd8e447 0 14 10333 2017-05-14T12:42:19Z Kazmuth 35 Created page with "__TOC__ *'''Here are the most asked questions from Pinoy Waze Editors''' ==Is there a manual for Waze map editing?== There is a [[Waze Map Editor]] manual that applies to b..." wikitext text/x-wiki __TOC__ *'''Here are the most asked questions from Pinoy Waze Editors''' ==Is there a manual for Waze map editing?== There is a [[Waze Map Editor]] manual that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [http://www.waze.com/wiki/index.php?title=Philippines Editing Resources for the Philippines] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[Best map editing practice]] guide in the wiki. However, some items listed on our guide are specifically for our pinoy roads and driving habits. ==I've been blocked and I can't edit on WME or send a report through the app== If you have received a message on the app or an email notification that you have been blocked, this is because of either 1. You have been detected by the Waze system as massively reporting. or 2. You have been reported by the community because you are violating the rules imposed by Waze and/or the community. If #1 is the case, even if we could, we will not help you with this. Like Waze, we do not tolerate cheating, and will not lift a finger to help you get unblocked or unbanned. By spamming the reports function you intentionally send out wrong, inconsistent, spurious, or unneeded data. You are also skewing the data being collected by Waze making the aggregate data inaccurate. If you fall under #2 then what you should do is 1. Read the wiki, particularly the [[Philippines]] section so you can figure out what you did wrong 2. Join the [https://www.facebook.com/groups/WazePhilippines/ Waze Philippines FB Group] 3. Join the [https://telegram.me/joinchat/AgCmlz-Od3QQPKjAHl_OMQ Waze Philippines Telegram channel] 4. Post a message on the FB group or the Telegram channel and tell us your predicament. If you fail to read the wiki or figure out why you were blocked, we will not help you. ==Why am I not leveling up to Level 2 or 3?== We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]), have joined at least 1 [[Philippines/MapRaid_History|PH MapRaid]], have attended the "Intro to Map Editing Webinar", and have joined the [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg PH Telegram channel]. This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] ==How do I apply to be an Area Manager?== To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] ==How long does it take until my edits gets displayed on my waze client?== It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area ==When I encounter traffic on the road, what type do I report?== You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; ==Standstill traffic== - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) ==Heavy traffic== - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. ==Moderate traffic== - Speed is usually 10 to 25 kph ==I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?== The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are NO ROADS which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them ==What is the difference between Map Issues and Update Requests?== Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues. ==How do I fix Map Issues?== Visit the [https://wiki.waze.com/wiki/MP Map Issues] wiki for more details. ==How do I fix Update Requests?== Visit the [https://wiki.waze.com/wiki/Update_requests Update Requests] wiki for more details. ==Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?== On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. ==Waze does not use the U-Turn segment I created between two roads, what could be the problem?== Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. ==Are there any shortcut keys for the Waze Map Editor?== You can view the wiki page on [[Keyboard shortcuts]] ==Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?== Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. ==I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?== You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. ==The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?== The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. ==There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?== You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the [[Scheduled restrictions]] wiki. ==Search function doesn't work, how do I fix it?== This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. ==I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?== If refreshing the map editor does not work, go to [http://status.waze.com the waze status page] and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==How do I report flooding so that wazers will not be routed on a flooded road?== Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report an unpassable road due to flooding, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank, and the country. *The road will be opened when Waze detects that a number of users have driven through the road. [[Category:Philippines]] 6b4fa807ed03ff22ccee8f0a3fe859f058659506 10339 10333 2017-05-14T13:19:39Z Kazmuth 35 wikitext text/x-wiki __TOC__ *'''Here are the most asked questions from Pinoy Waze Editors''' ==Is there a manual for Waze map editing?== There is a [[global:Waze_Map_Editor|Waze Map Editor]] manual that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [[Philippines/Editing resources |Editing Resources for the Philippines]] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed on our guide are specifically for our pinoy roads and driving habits. ==I've been blocked and I can't edit on WME or send a report through the app== If you have received a message on the app or an email notification that you have been blocked, this is because of either 1. You have been detected by the Waze system as massively reporting. or 2. You have been reported by the community because you are violating the rules imposed by Waze and/or the community. If #1 is the case, even if we could, we will not help you with this. Like Waze, we do not tolerate cheating, and will not lift a finger to help you get unblocked or unbanned. By spamming the reports function you intentionally send out wrong, inconsistent, spurious, or unneeded data. You are also skewing the data being collected by Waze making the aggregate data inaccurate. If you fall under #2 then what you should do is 1. Read the wiki, particularly the [[Philippines]] section so you can figure out what you did wrong 2. Join the [https://www.facebook.com/groups/WazePhilippines/ Waze Philippines FB Group] 3. Join the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg Waze Philippines Telegram channel] 4. Post a message on the FB group or the Telegram channel and tell us your predicament. If you fail to read the wiki or figure out why you were blocked, we will not help you. ==Why am I not leveling up to Level 2 or 3?== We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]), have joined at least 1 [[Philippines/MapRaid_History|PH MapRaid]], have attended the "Intro to Map Editing Webinar", and have joined the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg PH Telegram channel]. This means all Waze editors will be forced ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] ==How do I apply to be an Area Manager?== To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[global:Area_Manager|Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] ==How long does it take until my edits gets displayed on my Waze app?== It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area ==When I encounter traffic on the road, what type do I report?== You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph ==I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?== The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are '''NO ROADS''' which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, and most Expressways. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps because of report abuse. You will still be able to report them but they will no longer appear on WME and you will not get any points for them. ==What is the difference between Map Problems and Update Requests?== Map Problems or MPs are Waze generated and based on analyzed Wazer traffic. Update Requests or URs are Waze user submitted requests to fix user identified map issues. ==How do I fix Map Problems?== Visit the [[global:Map_Problems_in_Waze_Map_Editor|Map Problem]] wiki for more details. ==How do I fix Update Requests?== Visit the [[global:Update_Requests_in_Waze_Map_Editor|Update Requests]] wiki for more details. ==Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?== On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. ==Waze does not use the U-Turn segment I created between two roads, what could be the problem?== Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. ==Are there any shortcut keys for the Waze Map Editor?== You can view the wiki page on [[global:Keyboard_shortcuts|Keyboard shortcuts]] ==Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?== Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. ==I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?== You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. ==The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?== The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. ==There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?== You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the Partial[[global:Partial_restrictions| restrictions]] wiki. ==Search function doesn't work, how do I fix it?== This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. ==I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?== If refreshing the map editor does not work, go to [http://status.waze.com the Waze status page] and check for any announcement from Waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==How do I report flooding so that Wazers will not be routed on a flooded road?== Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report an unpassable road due to flooding, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank, and the country. *The road will be opened when Waze detects that a number of users have driven through the road. [[Category:Philippines]] 5da0e95274cbf7c64f45ec61e0b203144b41862e 0 5 10337 10220 2017-05-14T12:55:37Z Kazmuth 35 /* Philippine Locking Policy */ wikitext text/x-wiki __TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are; 1. Already is almost complete and accurate. If an area is already considered complete, they may be locked to Level 5 for Freeway/Major/Minor Highways, Level 4 for Primary roads, and L3 for everything else. The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. 2. Changes or edits to these segments are seldom done or does not happen that often. 3. Segments that are high value roads where incorrect edits will result in routing issues. 4. Vandalism on the Waze maps 5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Primary Streets'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Airports'''&nbsp;- should be locked at L6 to prevent accidental edit and deletion. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' All named segments will be locked to level 3. '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Places''' All places will be locked to level 4 to prevent unnecessary edits. This will ensure that all edits will be approved by the local champs only. *'''What not to lock''' Unnamed roads and segment in NCR should be locked to level 2 and those outside NCR should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. [[Category:Philippines]] 03861af6286e0b9e5fcca1a3ee967692250813bc 10354 10337 2017-05-16T17:46:27Z Adabadada 39 /* Philippine Locking Policy */ wikitext text/x-wiki __TOC__ == Philippine Locking Policy == *'''Introduction''' This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy The primary reason for locking an area or segments is because they are: 1. Almost complete and accurate. If an area is already considered complete, they may be locked to Level 5 for Freeway/Major/Minor Highways, Level 4 for Primary roads, and L3 for everything else. The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted. 2. Changes or edits to these segments are seldom done or does not happen that often. 3. Segments that are high value roads where incorrect edits will result in routing issues. 4. Vandalism on the Waze maps 5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted *'''Road Types''' '''NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.''' '''Expressways'''&nbsp;- are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs '''Major Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Minor Highways'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Primary Streets'''&nbsp;- should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits. '''Airports'''&nbsp;- should be locked at L6 to prevent accidental edit and deletion. '''Railroads'''&nbsp;- should be locked at L5 to prevent accidental edit and deletion. *'''Other Situations''' '''Junctions / Intersections and Roundabouts''' These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions. '''Ordinary Streets and other road types''' All named segments will be locked to level 3. '''Roads Not Matching Aerials''' With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials. '''Places''' All places will be locked to level 4 to prevent unnecessary edits. This will ensure that all edits will be approved by the local champs only. *'''What not to lock''' Unnamed roads and segment in NCR should be locked to level 2 and those outside NCR should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned. [[Category:Philippines]] 45455ae692fc50ebf42e5fe111f2a29d13ac97c7 0 2 10338 10330 2017-05-14T12:58:16Z Kazmuth 35 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads\ * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set road type attributes. * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines - A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 12. '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 1ed312e774795edee4d0ec3af76bf0e5c045991f 10351 10338 2017-05-16T15:13:50Z Adabadada 39 /* Map Editing Guide for the Philippines */ minor format changes wikitext text/x-wiki == Map Editing Guide for the Philippines == While most of the content here on the Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set road type attributes. * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 12. '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 9974ff5a500ad5247d5207b67540974025d6b471 0 3 10340 10210 2017-05-14T13:21:08Z Kazmuth 35 /* Philippines MapRaid History */ wikitext text/x-wiki == Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. We first heard about the concept during the official Philippines Waze Meetup conducted June 2014. From there, we coordinated with Waze on the mechanics of the effort. Visit the [[global:MapRaid|MapRaid]] wiki for more details. Here are some of the stats from the MapRaids that were done on the Philippines {| class="wikitable sortable" |- ! Date !! Location !! # of Raiders !! Segments Handled !! Segments Created !! MPs Resolved !! URs Resolved !! PUs Handled !! Previous Connectivity !! New Connectivity !! Change |- | Sept 2014 || Metro Manila || 10 || 3104 || 877 || 8 || 255 || 577 || 88.74% || 95.213% || 6.473% |- | Oct 2014 || Central Luzon || 14 || 136619 || 46810 || 772 || 3290 || 9529 || || || |- | Nov 2014 || Cavite and Laguna || 14 || 25702 || 8492 || 35 || 209 || 4200 || || || |- | Feb 2015 || Metro Manila || 16 || 26930 || 5396 || 0 || 3070 || 6411 || 93.6% || 95.5% || 1.9% |- | Dec 2015 || Metro CDO || 8 || 21324 || 8466 || 0 || 54 || 476 || 93.28% || 96.8% || 3.52% |- | Dec 2015 || Metro Cebu || 9 || 19653 || 6914 || 0 || 190 || 4363 || 97.72% || 98.4% || 0.68% |- | Dec 2015 || Metro Davao || 9 || 55917 || 23835 || 0 || 58 || 1921 || 96.94% || 97.7% || 0.76% |} [[Category:Philippines]] 0c44d4f4b60c6276f2ef142eb4b56086739dacc7 10352 10340 2017-05-16T17:33:32Z Adabadada 39 /* Philippines MapRaid History */ Added details for April 2016 mapraid wikitext text/x-wiki == Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. We first heard about the concept during the official Philippines Waze Meetup conducted June 2014. From there, we coordinated with Waze on the mechanics of the effort. Visit the [[global:MapRaid|MapRaid]] wiki for more details. Here are some of the stats from the MapRaids that were done on the Philippines {| class="wikitable sortable" |- ! Date !! Location !! # of Raiders !! Segments Handled !! Segments Created !! MPs Resolved !! URs Resolved !! PUs Handled !! Previous Connectivity !! New Connectivity !! Change |- | Sept 2014 || Metro Manila || 10 || 3104 || 877 || 8 || 255 || 577 || 88.74% || 95.213% || 6.473% |- | Oct 2014 || Central Luzon || 14 || 136619 || 46810 || 772 || 3290 || 9529 || || || |- | Nov 2014 || Cavite and Laguna || 14 || 25702 || 8492 || 35 || 209 || 4200 || || || |- | Feb 2015 || Metro Manila || 16 || 26930 || 5396 || 0 || 3070 || 6411 || 93.6% || 95.5% || 1.9% |- | Dec 2015 || Metro CDO || 8 || 21324 || 8466 || 0 || 54 || 476 || 93.28% || 96.8% || 3.52% |- | Dec 2015 || Metro Cebu || 9 || 19653 || 6914 || 0 || 190 || 4363 || 97.72% || 98.4% || 0.68% |- | Dec 2015 || Metro Davao || 9 || 55917 || 23835 || 0 || 58 || 1921 || 96.94% || 97.7% || 0.76% |- |April 2016 |NCR |22 |41400 |4100 |0 |2500 |24700 |94% |95.3% |1.3% |} [[Category:Philippines]] d26065e379784d35bcd34fc52b5f707b6da7c7da 0 4 10341 10213 2017-05-14T13:25:45Z Kazmuth 35 /* Guidelines for Resolving Update Requests (UR) */ wikitext text/x-wiki __TOC__ == Guidelines for Resolving Update Requests (UR) == *'''Introduction''' User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs *'''Priority URs''' We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest. *'''Steps on resolving URs''' Visit the [[global:Update_Requests_in_Waze_Map_Editor|Update Requests]] wiki for more details on how to resolve URs. '''NOTE:''' As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met; *a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the Update Request closing policy below. *b. reporter has agreed that UR is not an issue, mark the UR as Solved *c. issue has been resolved, mark the UR as Solved == Update Request (UR) closing policy == The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the city level or 200m/1000ft and counting the number of URs (MPs excluded). Heavy > 10 Mid 5 to 10 Light < 5 On areas with heavy UR density, we ask for a follow up after 1 day and then close the UR if still no reply after another day. For mid UR density, it will be follow up after 2 days and then close if no reply after another 2 days. And for light UR density, it will be follow up after 3 days and then close if no reply after another 3 days. For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area. The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed. Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map. [[Category:Philippines]] cde99c1c940717160d9f0313ea9a214cdd044c60 0 6 10342 10228 2017-05-16T10:35:18Z Adabadada 39 Changed Dominatrix to Adabadada Minor format changes wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager <u>iPhone expert</u> * deadlockprocess * shogsbro <u>Android expert</u> * zy_pher * Guardian4ngel * shogsbro <u>WME Editing expert</u> * zy_pher * Guardian4ngel * deadlockprocess * shogsbro <u>WME Beta Editor expert</u> * kazmuth * Baldugaras <u>Navigation / Routing expert</u> * deadlockprocess * shogsbro <u>Social Media expert</u> * zy_pher * Guardian4ngel * Adabadada <u>Localization expert</u> * kazmuth <u>Local Champs</u> * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie <u>Wiki Masters</u> * rccoros * kazmuth == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | roseAntonio | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | furuboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 6158366eda9d62b5bf495a5e2ee0e0e4ab4a4846 0 7 10343 10240 2017-05-16T12:14:19Z Adabadada 39 Edited intro, headings wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === '''New Places'''<br /> When adding new Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. Also make sure that it is not a duplicate of an already existing place, either an area place or a point place. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are;<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues'''. So if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :'''Gas Stations''' - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 0c98fcead921bc7598e19427a5a1bf8e723c25da 10344 10343 2017-05-16T12:20:16Z Adabadada 39 Edited Gas stations, added parking lots wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === '''New Places'''<br /> When adding new Places, make sure their location is properly identified through the add Area Places draw function and add the address in the details as well. Also make sure that it is not a duplicate of an already existing place, either an area place or a point place. If an Area Place will cover beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are:<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues'''. So if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :Special note for places: :'''Gas Stations''' - Gas stations should always be mapped as Area Places. When adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. :'''Parking Lots''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 56fc546502899310a6988fd8bb960a15cd7f6bfb 10345 10344 2017-05-16T12:42:43Z Adabadada 39 /* EDITING PLACES */ Elaborated on how to add a new place and appropriate details. wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === '''New Places'''<br /> The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). If an Area Place will cover beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The main differences for these are:<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues'''. So if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place. Compounds and buildings fall into this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :Special note for places: :'''Gas Stations''' - Gas stations should always be mapped as Area Places. When adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. :'''Parking Lots''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 12c0dfb0e28a3d0ff09c5e62d8ddf2212a1bd896 10346 10345 2017-05-16T13:05:58Z Adabadada 39 /* EDITING PLACES */ added guidelines for what kinds of places should be added, edited new place handling, edited place types wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === '''New Places'''<br /> Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. The two place types are:<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :Special note for places: :'''Gas Stations''' - Gas stations should always be mapped as Area Places. When adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. :'''Parking Lots''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 648589fa02fb0f539c4f50bd88d7364ed97de42b 10347 10346 2017-05-16T13:32:24Z Adabadada 39 /* EDITING PLACES */ Added Naming Places wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === '''New Places'''<br /> Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. <u>Place types</u>:<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. : :Special note for places: :'''Gas Stations''' - Gas stations should always be mapped as Area Places. When adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. :'''Parking Lots''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. <u>Naming Places:</u> For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. It is recommended that you add all possible iterations of the name that you think an ordinary Wazer might use to search for the place - so the acronym may be used but also spell out the name. Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 5a28971266b0c4a235a987a9066008dbec96761e 10348 10347 2017-05-16T13:54:40Z Adabadada 39 /* EDITING PLACES */ Added "Other Place Details" wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === '''New Places'''<br /> Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. <u>Place types</u>:<br /> :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. : :Special note for places: :'''Gas Stations''' - Gas stations should always be mapped as Area Places. When adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. :'''Parking Lots''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. :'''Residence/Home''' - In general we do not use this category becuase once saved the name will automatically be removed. If you see any place using this category, choose a more appropriate category and find the appropriate name. :'''Residential''' - These are private residences that will not be publicly searchable. The minimum details necessary for these places are correct address with house number, and a picture of the exterior. :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. <u>Naming Places:</u> For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. It is recommended that you add all possible iterations of the name that you think an ordinary Wazer might use to search for the place - so the acronym may be used but also spell out the name. <u>Other Place Details:</u> * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 2ffca77dd101b753d182ad71620866083ddef860 10349 10348 2017-05-16T14:26:05Z Adabadada 39 /* EDITING PLACES */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === ==== '''New Places''' ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Stations''' - Gas stations should always be mapped as Area Places. When adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. :'''Parking Lots''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - In general we do not use this category becuase once saved the name will automatically be removed. If you see any place using this category, choose a more appropriate category and find the appropriate name. :'''Residential''' - These are private residences that will not be publicly searchable. The minimum details necessary for these places are correct address with house number, and a picture of the exterior. :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. It is recommended that you add all possible iterations of the name that you think an ordinary Wazer might use to search for the place - so the acronym may be used but also spell out the name. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 1840d3977c56d6cbf743dd0f2d45aa411efe5773 10350 10349 2017-05-16T14:40:16Z Adabadada 39 /* Place Types */ Edited Area Places and Parking Lots, minor spelling changes wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === ==== '''New Places''' ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. When adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave it unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - In general we do not use this category because once saved the name will automatically be removed. If you see any place using this category, choose a more appropriate category and rename it. :'''Residential''' - These are private residences that will not be publicly searchable. The minimum details necessary for these places are correct address with house number, and a picture of the exterior. :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. It is recommended that you add all possible iterations of the name that you think an ordinary Wazer might use to search for the place - so the acronym may be used but also spell out the name. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 8d934938bbc2f1181abb4f9d98b7f6deb7b25f64 10356 10350 2017-05-17T05:16:16Z Adabadada 39 /* EDITING PLACES */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. When adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave it unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - In general we do not use this category because once saved the name will automatically be removed. If you see any place using this category, choose a more appropriate category and rename it. :'''Residential''' - These are private residences that will not be publicly searchable. The minimum details necessary for these places are correct address with house number, and a picture of the exterior. :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. It is recommended that you add all possible iterations of the name that you think an ordinary Wazer might use to search for the place - so the acronym may be used but also spell out the name. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === '''Reviewing New Places'''<br /> '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> '''Pictures'''<br /> Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> '''Updates on Places' Information'''<br /> The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 8432dffe819974c6781cde469a47691771ade1cf 10357 10356 2017-05-17T11:54:39Z Adabadada 39 /* HANDLING PLACE UPDATE REQUESTS */ Formatting - fixed sub-headings wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. When adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave it unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - In general we do not use this category because once saved the name will automatically be removed. If you see any place using this category, choose a more appropriate category and rename it. :'''Residential''' - These are private residences that will not be publicly searchable. The minimum details necessary for these places are correct address with house number, and a picture of the exterior. :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. It is recommended that you add all possible iterations of the name that you think an ordinary Wazer might use to search for the place - so the acronym may be used but also spell out the name. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === ==== Reviewing New Places<br /> ==== '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 4e614a8860ecd8cccb875cc40038bdd4b88e0b91 10358 10357 2017-05-17T12:35:22Z Adabadada 39 /* Special Place Categories */ expounded category descriptions wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave it unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu but is still in use for some old places. In general we do not use this category because places under this category are considered private residences and are not searchable on the app. The names of places have been automatically removed. If you see any place using this category, choose a more appropriate category and rename it. :'''Residential''' - These are private residences that will not be publicly searchable. These can only be added by Wazers using the client. The minimum details necessary for these places are correct address with house number, and a picture of the exterior. :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. It is recommended that you add all possible iterations of the name that you think an ordinary Wazer might use to search for the place - so the acronym may be used but also spell out the name. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === ==== Reviewing New Places<br /> ==== '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 81aea1a9ef6b20ce047f33965b0fab30b40e9630 10359 10358 2017-05-17T13:20:37Z Adabadada 39 Minor grammar edit to Place Types; Expounded on naming business franchises, added naming place-within-a-place, expounded on alternative names. wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu but is still in use for some old places. In general we do not use this category because places under this category are considered private residences and are not searchable on the app. The names of places have been automatically removed. If you see any place using this category, choose a more appropriate category and rename it. :'''Residential''' - These are private residences that will not be publicly searchable. These can only be added by Wazers using the client. The minimum details necessary for these places are correct address with house number, and a picture of the exterior. :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === ==== Reviewing New Places<br /> ==== '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 841a0cf5424c8228108671b476f0a13383b6bc79 10360 10359 2017-05-17T13:25:26Z Adabadada 39 /* Philippine Places Policy */ Edited introduction wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lots categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu but is still in use for some old places. In general we do not use this category because places under this category are considered private residences and are not searchable on the app. The names of places have been automatically removed. If you see any place using this category, choose a more appropriate category and rename it. :'''Residential''' - These are private residences that will not be publicly searchable. These can only be added by Wazers using the client. The minimum details necessary for these places are correct address with house number, and a picture of the exterior. :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === ==== Reviewing New Places<br /> ==== '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 914828a0926d89e2cda938510099af0a64af6ea2 10361 10360 2017-05-17T13:31:07Z Adabadada 39 /* Special Place Categories */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu but is still in use for some old places. In general we do not use this category because places under this category are considered private residences and are not searchable on the app. The names of these places have been automatically removed. If you see any place using this category, choose a more appropriate category and rename it. :'''Residential''' - These are private residences that will not be publicly searchable. These can only be added by Wazers using the client. The minimum details necessary for these places are correct address with house number, and a picture of the exterior. :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === ==== Reviewing New Places<br /> ==== '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] af2a493edceb09c2f3f7facbb91300137a9a85dc 10362 10361 2017-05-17T13:44:41Z Adabadada 39 /* Special Place Categories */ Merged Residences/Home and Residential wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === ==== Reviewing New Places<br /> ==== '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] f831f00b910add1e79abef4e4626f77430ea5ea4 10363 10362 2017-05-17T14:43:23Z Adabadada 39 /* Reviewing New Places */ Added kinds of new places, definitions, how to decide when to approve places. wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. For "New place" PURs for private residences, approve only places with a valid address (house number required). Make sure the location is correct. Once done, add the edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br /> *If the new area contains more information or detail than the existing area, copy these information over to the old place and then reject the new place submission. <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] dc4c7dcbd7a7ff55274ab6f7b6f202221bbb716c 10364 10363 2017-05-17T15:00:23Z Adabadada 39 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs for private residences, approve only places with a valid address (house number required). Make sure the location is correct. Once done, add the edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) *Correct capitalization and spelling of Place Name '''Reject'''<br /> *Places that are actually roads *Duplicate places *Incorrect capitalization and spelling *Incorrect information <br />*A note on duplicate places: *If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] fbd70eba9c84e1f732fe5dd8bd7febc316ed08cc 10365 10364 2017-05-17T15:58:31Z Adabadada 39 /* Reviewing "New Place" Reports */ added specific guidelines for approving and rejecting new place submissions wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR. *Incorrect information <br /> <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] 1a8f7edb8fa58d1066cb03b01ed038f51375520f 10366 10365 2017-05-17T16:08:34Z Adabadada 39 /* Reviewing "New Place" Reports */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.<br /> '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] a7e76bfeeb44ff70ca20e65c4eb8a128f13971d0 10367 10366 2017-05-17T16:23:55Z Adabadada 39 /* Reviewing "New Place" Reports */ moved info about blacklisted users to a different section, added info on becoming a trusted user. wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. Any user can be distrusted if they submit a certain number of PURs which have been rejected. However, users will can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] d5d31e673b1d3f18b5283cd5fcdf013118ae1537 10368 10367 2017-05-17T16:35:06Z Adabadada 39 /* Reviewing "New Place" Reports */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. Please note the hyphen between the business name and branch name. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a hyphen). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. Any user can be distrusted if they submit a certain number of PURs which have been rejected. However, users will can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Updates on Places' Information<br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] a9ce8d983f2f5a0c89dd421a51e66b17157c1cb7 10369 10368 2017-05-17T16:54:58Z Adabadada 39 /* Pictures */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. Any user can be distrusted if they submit a certain number of PURs which have been rejected. However, users will can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== The general guideline to use to determine whether to Accept the update is, '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers, just the official street names. ''"Is the majority of information provided in the update correct?"'' A Place update, if the user completes ALL the information, can be extremely long Even if some of the data is incorrect, or the photo included in the update improper and unhelpful to drivers, the editor can still remove the photo or update/delete the incorrect information after accepting the update. It is better, faster, and more honest to accept the good information from the driver, and fix the problems, rather than rejecting the entire update and filling in the info yourself. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization *Converting to Residence/Home if the place is not a house *If it is a private residence but does not contain a street number and street name [[Category:Philippines]] f9df2eda87c0293b3d5780e89f1e5a81122c1af4 10370 10369 2017-05-17T17:42:08Z Adabadada 39 /* Reviewing "New Details for Place" Reports  */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. Any user can be distrusted if they submit a certain number of PURs which have been rejected. However, users will can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many wazers like to add multiple services even if the establishment does not offer it, just to get extra points. '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== [[Category:Philippines]] 06377804f358b13e4a106d6d572c110ef9ea3ce8 10371 10370 2017-05-17T18:31:29Z Adabadada 39 /* Reviewing Flag Requests */ Added section on flag reasons and what to do about them. wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishments listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. Any user can be distrusted if they submit a certain number of PURs which have been rejected. However, users will can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many wazers like to add multiple services even if the establishment does not offer it, just to get extra points. '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 750c8b40b2dcf43dc452a66c1d32f040b329dd00 10374 10371 2017-05-17T19:04:33Z Adabadada 39 /* Other Place Details */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. When drawing an Area Place make sure to include the entire place including its parking lot. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. Make sure not to leave point places right on top of road segments. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs which have been rejected. However, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many wazers like to add multiple services even if the establishment does not offer it, just to get extra points. '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 3deecfff53180e37550d92f6615876a643d48719 10376 10374 2017-05-21T06:46:07Z Adabadada 39 Added pointers for placement of navigation point/place point wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :When drawing an Area Place make sure to include the entire place ''including its parking lot''. The parking lot then has to be drawn as another Area Place within the bigger establishment. :When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. :''<u>Placement of the navigation point:</u>'' :Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. :DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :DO NOT leave a point place right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: we use Title Case for all place names regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: <Business Name> - <Branch/Locator>. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA) * External Providers: check if auto-linked places are correct. Manually link places that may be at the wrong location. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs which have been rejected. However, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many wazers like to add multiple services even if the establishment does not offer it, just to get extra points. '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 22d7ddf0b1397cd1308c9cb258469768d484664c 10377 10376 2017-05-21T06:58:10Z Adabadada 39 /* EDITING PLACES */ Minor format changes to Naming Places, expounded on Addresses and External Providers wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :When drawing an Area Place make sure to include the entire place ''including its parking lot''. The parking lot then has to be drawn as another Area Place within the bigger establishment. :When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. :''<u>Placement of the navigation point:</u>'' :Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. :DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :DO NOT leave a point place right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * External Providers: Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs which have been rejected. However, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many wazers like to add multiple services even if the establishment does not offer it, just to get extra points. '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] d7c488ae6aef4eaef27a74c61a44adce012a69d5 10378 10377 2017-05-21T07:08:11Z Adabadada 39 /* HANDLING PLACE UPDATE REQUESTS */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :When drawing an Area Place make sure to include the entire place ''including its parking lot''. The parking lot then has to be drawn as another Area Place within the bigger establishment. :When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. :''<u>Placement of the navigation point:</u>'' :Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. :DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :DO NOT leave a point place right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * External Providers: Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places. If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing '''Reject''' *House or residence images set to public viewing *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many wazers like to add multiple services even if the establishment does not offer it, just to get extra points. '''Adding place addresses'''<br /> When adding the address of a place, add the number if you know it or add the street name. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 37ae57a8b19fae62e37f04bd25179c79de2123e6 10379 10378 2017-05-21T07:29:34Z Adabadada 39 /* Reviewing "New Place" Reports */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places, and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :When drawing an Area Place make sure to include the entire place ''including its parking lot''. The parking lot then has to be drawn as another Area Place within the bigger establishment. :When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. :''<u>Placement of the navigation point:</u>'' :Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. :DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :DO NOT leave a point place right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * External Providers: Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 7b47a1a5eb69c95bd50af73753caa26604f27c61 0 13 10353 10325 2017-05-16T17:39:03Z Adabadada 39 Split the sentence wikitext text/x-wiki The speedlimits in the Philippines are stated in [http://www.gov.ph/1964/06/20/republic-act-no-4136/ REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed.'' They are as follows: {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads, On/Off Ramps || 40 || 40 |- | Streets, except those with speedbumps (humps) || 30 || 30 |- | Private & Parking Lot roads, Streets with speedbumps (humps) || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} [[Category:Philippines]] 83924bc09a2176efc82a878ff021ca65abdcdce2 10 15 10380 2017-05-21T14:52:51Z Wottem 25 Created page with "'''TestMe'''" wikitext text/x-wiki '''TestMe''' 4ad80d7bb1f61a438da08a517313d1a8f953ad71 10 15 10381 10380 2017-05-21T17:07:11Z Wottem 25 1 revision imported from [[:global:Template:TestMe]]: Bot Script Sync Templates wikitext text/x-wiki '''TestMe''' 4ad80d7bb1f61a438da08a517313d1a8f953ad71 0 7 10382 10379 2017-05-23T07:07:01Z Adabadada 39 /* Special Place Categories */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places), and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :When drawing an Area Place make sure to include the entire place ''including its parking lot''. The parking lot then has to be drawn as another Area Place within the bigger establishment. :When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. :''<u>Placement of the navigation point:</u>'' :Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. :DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :DO NOT leave a point place right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :Point Places need not be located right where the establishment is physically located. We put Point Places close to the road segment nearest to the actual place, taking into consideration that it is at this point that the Wazer will be told he/she has arrived. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (he name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * External Providers: Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] c21718852129b7019c4c92faa46488083eea4752 10383 10382 2017-05-24T13:03:05Z Adabadada 39 /* Place Types */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places), and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :When drawing an Area Place make sure to include the entire place ''including its parking lot''. The parking lot then has to be drawn as another Area Place within the bigger establishment. :When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. :''<u>Placement of the navigation point:</u>'' :Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. :DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (he name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * External Providers: Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 689677ebb5fc0d031d2da819065cf53358976ed7 10403 10383 2017-05-28T18:52:21Z Adabadada 39 /* Place Types */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places), and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :* When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination. :* When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do. :* Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map. :* When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app. :''<u>Placement of the navigation point:</u>'' :* Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. :* For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place. :* DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (he name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). Ex. Building A - Alphabet Estates Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. Ex. Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * External Providers: Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] ea46fb986576150eb783bafc2b3ff24a7af5bb59 10404 10403 2017-05-28T19:03:48Z Adabadada 39 /* Place Types */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places), and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators though they also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :* When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination. :* When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do. :* Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map. :* When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app. :''<u>Placement of the navigation point:</u>'' :* Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. :* For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place. :* DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :* DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :* Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. These two don't always have to be separated, and it is perfectly acceptable to keep these joined as long as routing will remain correct and the point place is not too far from its actual location. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (he name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== * For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. * For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' * For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). '''Example -''' Building A - Alphabet Estates * Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. '''Example''' Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie Name: D and E Enterprises ; Alternative Names: D & E Enterprises, D & E Ent., D and E Ent. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" and remove any slash (/) at the end * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * External Providers: Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] b15308cadf2ea9d861a8829fda8e80cb845791f4 0 1 10384 10375 2017-05-28T08:11:11Z Adabadada 39 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Guidelines for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 1007107f612508e2ae7d4ce5263fb8734e17589d 10406 10384 2017-05-28T19:28:35Z Adabadada 39 /* Editing Guidelines for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Guidelines for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our Pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 68d5594b6af27bbc537fa1715ef22d4858f6bdc4 10408 10406 2017-05-28T19:38:41Z Adabadada 39 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Guidelines for the Philippines== * [[Philippines/Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our Pinoy roads and driving habits. * [[Philippines/Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 29513e0efde3eb1da96c6ef8fb648592f9a189d4 10411 10408 2017-05-29T10:57:18Z Kazmuth 35 /* Editing Guidelines for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] {{:Getting Started}} == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our Pinoy roads and driving habits. * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] d30b44044a2c3ecca407e78ba5b697b73ad9f27d 10413 10411 2017-05-29T12:51:35Z Adabadada 39 Added new Section: New to Editing wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our Pinoy roads and driving habits. * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 5fc6b0bba27a47fbb738e959100ede19ce89ee61 10414 10413 2017-05-29T14:26:01Z Adabadada 39 /* New to Editing? Start Here */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[wazeopedia.waze.com/wiki/UnitedKingdom/Quick Start|Quick Start]] * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] * Best map editing practice == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our Pinoy roads and driving habits. * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 4ccdd60d139bcd9f4c57bb0833d3ddf109852b39 10415 10414 2017-05-29T14:28:05Z Adabadada 39 /* New to Editing? Start Here */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] * Best map editing practice == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our Pinoy roads and driving habits. * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 384e26bd0a246dbadf7f8505cb824c2a79751be8 10418 10415 2017-05-29T15:05:02Z Adabadada 39 /* New to Editing? Start Here */ Added links for Editing and Best map editing practice wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[global:Map_Editing_Quick-start_Guide|Map Editing Quick Start]] * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] * [[global:Best_map_editing_practice|Best map editing practice]] * [[global:Editing_manual|Editing Manual]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our Pinoy roads and driving habits. * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] f10f8b581d40b46ae84349622fe786eac1ed52f8 10419 10418 2017-05-29T15:07:10Z Adabadada 39 /* New to Editing? Start Here */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section is under construction for the PH. Links to other Global/Local Pages for now) * [[global:Map_Editing_Quick-start_Guide|Map Editing Quick Start]] * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES:''' [[usa:Edits_to_avoid|Edits to avoid]] * [[global:Best_map_editing_practice|Best map editing practice]] * [[global:Editing_manual|Editing Manual]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] - a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed are specifically for our Pinoy roads and driving habits. * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] adce0e5e94642b820f54f21b86a5e48b131030a9 10420 10419 2017-05-29T15:36:24Z Adabadada 39 /* Getting Started */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] * Best map editing practice == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] cbce2b8569bb8ceb97bf74a94c0bd4c98cb1ab84 10422 10420 2017-06-01T19:31:00Z Adabadada 39 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] * [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 9c4d9cf7332f09c1dfdba34a97f76f42fc0921ac 10428 10422 2017-06-08T12:56:25Z Adabadada 39 /* New to Editing? Start Here */ Fixed broken link for best map editing guidelines wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) - [[usa:Edits_to_avoid|Edits to avoid]] * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] eca82743ce1390274c0283433b3844b02998aa96 0 6 10385 10342 2017-05-28T14:42:56Z Adabadada 39 /* Philippine Waze Champs and Experts */ wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager <u>iPhone expert</u> * deadlockprocess * shogsbro <u>Android expert</u> * zy_pher * Guardian4ngel * shogsbro <u>WME Editing expert</u> * zy_pher * Guardian4ngel * deadlockprocess * shogsbro <u>WME Beta Editor expert</u> * kazmuth * Baldugaras <u>Navigation / Routing expert</u> * deadlockprocess * shogsbro <u>Social Media expert</u> * zy_pher * Guardian4ngel * Adabadada <u>Localization expert</u> * kazmuth <u>Local Champs</u> * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie <u>Wiki Masters</u> * rccoros * kazmuth * Adabadada == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | daxky | Angeles | 11/18/2013 |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | daxky | Batangas City | 11/18/2013 |- | junrex | Bicol (Region V) | 6/24/2013 |- | M-a-r-s | Bislig | 8/22/2013 |- | daxky | Boracay Island | 12/31/2013 |- | roseAntonio | Cabanatuan | 8/2/2013 |- | mponteres | Cabuyao | 8/22/2013 |- | ericbishop | CALABARZON (Region IV-A) | 7/5/2013 |- | monz98 | CALABARZON (Region IV-A) | 6/28/2013 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | tcajita | Calamba | 1/11/2014 |- | atjcamacho | Cavite Province | 6/23/2013 |- | BRM-BLK-BMW | Cavite Province | 7/4/2013 |- | abecedarian2380 | Cebu Province | 8/2/2013 |- | gerix28 | Cebu Province | 6/22/2013 |- | pinoyoutdoor | Cebu Province | 7/7/2013 |- | warfab | Cebu City | 8/14/2013 |- | world_8eidg3mz | Cebu City | 7/20/2013 |- | Calicantzaros | Central Luzon (Region III) | 7/2/2013 |- | kwithoor | Central Luzon (Region III) | 1/11/2014 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | gerix28 | Central Visayas (Region VII) | 6/28/2013 |- | nobs98 | Central Visayas (Region VII) | 7/8/2013 |- | M-a-r-s | Eastern Mindanao | 12/5/2013 |- | monz98 | Eastern NCR | 6/27/2013 |- | crgandionco | Leyte | 9/9/2013 |- | daxky | Lipa | 11/18/2013 |- | furuboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | warfab | Mandaue | 8/14/2013 |- | world_8eidg3mz | Mandaue | 7/20/2013 |- | markking1991 | Manila | 6/23/2013 |- | mponteres | Muntinlupa | 8/22/2013 |- | atjcamacho | NCR | 6/23/2013 |- | bdo2v | NCR | 7/4/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | Calicantzaros | NCR | 7/2/2013 |- | daxky | NCR | 11/18/2013 |- | furuboru | NCR | 6/23/2013 |- | kwithoor | NCR | 1/11/2014 |- | M-a-r-s | NCR | 7/7/2013 |- | mirallwood | NCR | 8/18/2013 |- | SEELE_01 | NCR | 1/29/2014 |- | SkipperBoo26 | NCR | 7/7/2013 |- | BRM-BLK-BMW | NCR | 7/4/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | markhaggai | Puerto Princesa | 8/30/2013 |- | ongandy86 | Quezon City | 8/30/2013 |- | crgandionco | Samar | 9/9/2013 |- | crgandionco | Southern Leyte | 12/21/2013 |- | tcajita | Sta Rosa | 1/11/2014 |- | kwithoor | Ilocos Region (Region I) | 3/11/2014 |- | kwithoor | Cagayan Valley (Region II) | 3/11/2014 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] d76055994dd76f88f1331314e3c7024ec54f6e05 10386 10385 2017-05-28T14:51:17Z Adabadada 39 /* Philippine Waze Area Manager */ removed inactive AMs wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager <u>iPhone expert</u> * deadlockprocess * shogsbro <u>Android expert</u> * zy_pher * Guardian4ngel * shogsbro <u>WME Editing expert</u> * zy_pher * Guardian4ngel * deadlockprocess * shogsbro <u>WME Beta Editor expert</u> * kazmuth * Baldugaras <u>Navigation / Routing expert</u> * deadlockprocess * shogsbro <u>Social Media expert</u> * zy_pher * Guardian4ngel * Adabadada <u>Localization expert</u> * kazmuth <u>Local Champs</u> * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie <u>Wiki Masters</u> * rccoros * kazmuth * Adabadada == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | SEELE_01 | Central Luzon (Region III) | 1/29/2014 |- | monz98 | Eastern NCR | 6/27/2013 |- | furuboru | Luzon Island Group | 8/8/2013 |- | ivanatorprime | Mandaluyong | 10/11/2013 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | SEELE_01 | NCR | 1/29/2014 |- |Guardian4ngel | NCR | 7/7/2013 |- | Dekca | Pampanga | 6/22/2013 |- | evs_13 | Pangasinan | 7/12/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | shogsbro | Northern Luzon | 6/22/2014 |- | swisspound2 | NCR | 3/31/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | albertcong | Cabadbaran | 6/25/2014 |- | albertcong | Surigao City | 6/25/2014 |- | albertcong | Butuan | 6/25/2014 |- | albertcong | Bislig | 6/25/2014 |- | palin_1274 | NCR | 6/27/2014 |- | palin_1274 | CALABARZON (Region IV-A) | 7/1/2014 |- | monz98 | Eastern NCR | 7/3/2014 |- | monz98 | CALABARZON (Region IV-A) | 7/3/2014 |- | albertcong | Caraga (Region XIII) | 7/10/2014 |- | SpeedyGonzalesAT | Metro Cebu | 8/5/2014 |- | kanamits | Negros Occidental Province | 8/5/2014 |- | gerix28 | Region VII | 10/6/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | cryptmaster | Bulacan Province | 11/29/2014 |- | SpeedyGonzalesAT | Cebu Province | 11/29/2014 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 427622210e4d786acdaec29bec5e60255becf236 10429 10386 2017-06-10T20:45:57Z Adabadada 39 Added new AMs wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager <u>iPhone expert</u> * deadlockprocess * shogsbro <u>Android expert</u> * zy_pher * Guardian4ngel * shogsbro <u>WME Editing expert</u> * zy_pher * Guardian4ngel * deadlockprocess * shogsbro <u>WME Beta Editor expert</u> * kazmuth * Baldugaras <u>Navigation / Routing expert</u> * deadlockprocess * shogsbro <u>Social Media expert</u> * zy_pher * Guardian4ngel * Adabadada <u>Localization expert</u> * kazmuth <u>Local Champs</u> * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie <u>Wiki Masters</u> * rccoros * kazmuth * Adabadada == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area ! scope="col" | Since |- | '''* deadlockprocess''' | Philippines | 2/22/2015 |- | shogsbro | Baguio | 2/17/2014 |- | Ungas | CALABARZON (Region IV-A) | 6/29/2013 |- | Ungas | Bicol (Region V) | 2/22/2015 |- | '''* zy_pher''' | Philippines | 2/22/2015 |- | SEELE_01 | NCR | 1/29/2014 |- |Guardian4ngel | NCR | 7/7/2013 |- | Dekca | Pampanga | 6/22/2013 |- | '''* baldugaras''' | Philippines | 8/7/2013 |- | iceden | Philippines | 6/25/2013 |- | '''* kazmuth''' | Philippines | 11/13/2012 |- | '''* rider111''' | Philippines | 6/21/2013 |- | '''* SpeedDzel''' | Philippines | 11/13/2012 |- | shogsbro | Northern Luzon | 6/22/2014 |- | '''* Lu_Wei_Jie''' | Philippines | 2/22/2015 |- | Adabadada | Cavite Province | 6/22/2014 |- | Guardian4ngel | Luzon Island Group | 10/9/2014 |- | Adabadada | NCR and Cavite | 11/2/2014 |- | Adabadada | CALABARZON (Region IV-A) | 2/22/2015 |- | Adabadada | Eastern Visayas (Region VIII) | 2/22/2015 |- | shogsbro | Luzon Island Group | 4/13/2015 |- | rccoros | NCR | 4/20/2015 |- | rock_stone | Cebu Province | 8/2/2015 |- | rccoros | CALABARZON (Region IV-A) | 8/3/2015 |- |'''*Adabadada''' |Philippines |12/18/2015 |- |Brezzypete | | |- |XMapperMG | | |- |Lukring | | |- |Mondskiez | | |- |jojob333 | | |- |kabutengkamote | | |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 032a05dfd3642c8310e5baed3bdd8ea1aeeb2088 0 2 10387 10351 2017-05-28T15:05:21Z Adabadada 39 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content here in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set road type attributes. * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 12. '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] a20584208873c873830c45747379692e8f94e953 10388 10387 2017-05-28T15:14:54Z Adabadada 39 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content here in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set road type attributes. * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 12. '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 9c7d507d4f003aea10e4b2c244fa4540345c1780 10389 10388 2017-05-28T15:15:38Z Adabadada 39 /* Note to all would-be editors in the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content here in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General guidelines on road editing === 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set road type attributes. * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 12. '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. [[Category:Philippines]] 70e7382f8293493ca9c3fd8fdfb64c7db0db92e0 10390 10389 2017-05-28T15:25:55Z Adabadada 39 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content here in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines. === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General guidelines on road editing === 1. Create road (whether tracing aerial images/gps points, or from recorded drives) 2. Set road type, some suggestions; * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set road type attributes. * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General guidelines on editing places === '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. [[Category:Philippines]] 9a11c962b7ec8800823240d880dc2169c700a2fe 10391 10390 2017-05-28T16:00:59Z Adabadada 39 /* General guidelines on road editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General guidelines on road editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[Best map editing practice]] for specifics. 2. Set road type, some suggestions; * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set road type attributes. * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General guidelines on editing places === '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. [[Category:Philippines]] 9499eaee0ced7db70f0ae22bb134c82c431a4521 10392 10391 2017-05-28T16:03:11Z Adabadada 39 /* General guidelines on road editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General guidelines on road editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Set road type, some suggestions; * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Set road type attributes. * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General guidelines on editing places === '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. [[Category:Philippines]] a55b783208c33ff427f7e948c790b18cb6bf165e 10393 10392 2017-05-28T17:40:25Z Adabadada 39 wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General guidelines on road editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Set directionality (two way or one way) 5. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Set the speed limits in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General guidelines on editing places === '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. [[Category:Philippines]] 298229643ad2ea4ec6c2b19c60b7858c5dfe3e46 10394 10393 2017-05-28T17:46:19Z Adabadada 39 /* General guidelines on road editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General guidelines on road editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parralel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Seting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway''' 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General guidelines on editing places === '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. [[Category:Philippines]] 59c4f16ec7119db659167f63b0dfacda8b131743 10395 10394 2017-05-28T17:50:59Z Adabadada 39 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General guidelines on road editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parralel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection even if they look like they are. All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows will appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction and placed 5m apart. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General guidelines on editing places === '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. [[Category:Philippines]] 07b21e4bff3d0ff230d4eaf3885eebbcecdcad05 10396 10395 2017-05-28T18:02:18Z Adabadada 39 /* General guidelines on road editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General guidelines on road editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parralel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road should be split if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' be split because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. '''Turn Lanes or at-grade connectors''' - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc When you are confident on an area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 13. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General guidelines on editing places === '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. [[Category:Philippines]] f947ccb72812834e58d91dde89b3a03b4513cf0c 10397 10396 2017-05-28T18:12:28Z Adabadada 39 /* General guidelines on road editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General guidelines on road editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General guidelines on editing places === '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. [[Category:Philippines]] c5c832fddbccbef6308753a1c6a7145c5cb55bb3 10398 10397 2017-05-28T18:15:38Z Adabadada 39 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === '''Adding Places''' - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. * '''Area Places''' - These primarily POI locators but also serve another function on the Waze map. They serve as '''navigation aids and cues''' so if a landmark serves as a navigation cue and is more than '''50m on it's X or Y coordinates''', you can add it. If it is smaller than 50m, consider adding a '''Point Place'''. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app. * '''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. [[Category:Philippines]] 1c1528ffd44a73c4b4b0e5afb67144f60cad060e 10399 10398 2017-05-28T18:26:32Z Adabadada 39 /* General Guidelines on Editing Places */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. [[Category:Philippines]] 7b37de063ba9f540c808ab4bbfa158d774a55c38 10400 10399 2017-05-28T18:28:23Z Adabadada 39 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. [[Category:Philippines]] b58a69111ee5b251073c50ba41638439dbac5b62 10409 10400 2017-05-29T10:16:24Z Adabadada 39 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === Major Traffic Events (MTE) are ______ look here for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Real-Time Closures === Real-time Closures (RTC) are _______ look here for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. [[Category:Philippines]] 1d4629682a2e2c7eef0046fc62df03dd839f3432 10410 10409 2017-05-29T10:22:52Z Adabadada 39 /* Map Editing Guide for the Philippines */ Added Real Time Closures wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === Major Traffic Events (MTE) are ______ look here for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable for some reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. [[Category:Philippines]] 864b3386a6b40dbe200ff5c704e526e92f9cea22 10412 10410 2017-05-29T12:43:28Z Adabadada 39 /* Real Time Closures */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. [[Category:Philippines]] eebf6072958077d9201b59f6f194bf8543b3600b 10421 10412 2017-05-29T19:32:53Z Adabadada 39 /* Major Traffic Events */ Added link for MTE wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. [[Category:Philippines]] e244f7753efb9e2c4b314f9a8645007685108b7d 10424 10421 2017-06-01T19:39:37Z Adabadada 39 /* Map Editing Guide for the Philippines */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. [[Category:Philippines]] c06ce8f93602b7f7d1e6d9ac096877a6bc64fe80 10425 10424 2017-06-01T19:42:38Z Adabadada 39 /* General Guidelines on Road Editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. [[Category:Philippines]] 43581c603c485f144d8d88bc94b548f1c7473243 10426 10425 2017-06-08T12:24:19Z Adabadada 39 /* Real Time Closures */ Added section about adding Map Comments to RTCs base on MapSir's forum post wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. [[Category:Philippines]] da5c3d1d7328da45f9d5707bb0d7f1010f4fdbe5 10427 10426 2017-06-08T12:26:00Z Adabadada 39 /* Real Time Closures */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[wazeopedia.waze.com/wiki/Philippines/Philippines/Places Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. [[Category:Philippines]] 91f636ede6ae2b30a170393db92abb02273eb22c 10430 10427 2017-06-18T08:38:06Z Kazmuth 35 /* General Guidelines on Editing Places */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name (DPWH Name) # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. [[Category:Philippines]] 1c9e14b3381f0ba7470d3607c8faf406b4d9fb01 0 16 10401 2017-05-28T18:33:28Z Adabadada 39 Added acronym meanings for DPWH and RNS wikitext text/x-wiki DPWH - Department of Public Works and Highways RNS - Route Numbering System fb9de07b4f05962535c392868b0355d0e7097eb1 10402 10401 2017-05-28T18:34:00Z Adabadada 39 wikitext text/x-wiki DPWH - Department of Public Works and Highways RNS - Route Numbering System b59baa4a898cf90535ac91f9ba32ca574c07db79 0 3 10405 10352 2017-05-28T19:26:45Z Adabadada 39 /* Philippines MapRaid History */ wikitext text/x-wiki == Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. The community first heard about the concept during the official Philippines Waze Meetup conducted June 2014. The first Philippine MapRaid was held in September 2014, with the raiders arranged into three teams, tackling problems in Metro Manila. Subsequent raids were then held in various provinces/cities throughout the country. The community has since been using MapRaids to improve community involvement, to discover new editing talent, and to train new editors by putting high-level editors in charge of running the teams and mentoring lower-level team members. Many editors have achieved level upgrade because of their performance in the MapRaids. Visit the [[global:MapRaid|MapRaid]] wiki for more details. Here are some of the stats from the MapRaids that were done in the Philippines {| class="wikitable sortable" |- ! Date !! Location !! # of Raiders !! Segments Handled !! Segments Created !! MPs Resolved !! URs Resolved !! PUs Handled !! Previous Connectivity !! New Connectivity !! Change |- | Sept 2014 || Metro Manila || 10 || 3104 || 877 || 8 || 255 || 577 || 88.74% || 95.213% || 6.473% |- | Oct 2014 || Central Luzon || 14 || 136619 || 46810 || 772 || 3290 || 9529 || || || |- | Nov 2014 || Cavite and Laguna || 14 || 25702 || 8492 || 35 || 209 || 4200 || || || |- | Feb 2015 || Metro Manila || 16 || 26930 || 5396 || 0 || 3070 || 6411 || 93.6% || 95.5% || 1.9% |- | Dec 2015 || Metro CDO || 8 || 21324 || 8466 || 0 || 54 || 476 || 93.28% || 96.8% || 3.52% |- | Dec 2015 || Metro Cebu || 9 || 19653 || 6914 || 0 || 190 || 4363 || 97.72% || 98.4% || 0.68% |- | Dec 2015 || Metro Davao || 9 || 55917 || 23835 || 0 || 58 || 1921 || 96.94% || 97.7% || 0.76% |- |April 2016 |NCR |22 |41400 |4100 |0 |2500 |24700 |94% |95.3% |1.3% |} [[Category:Philippines]] e76a6f1d0bae22016b13ad7d604cebd0e8195aff 0 14 10407 10339 2017-05-28T19:34:35Z Adabadada 39 /* Why am I not leveling up to Level 2 or 3? */ wikitext text/x-wiki __TOC__ *'''Here are the most asked questions from Pinoy Waze Editors''' ==Is there a manual for Waze map editing?== There is a [[global:Waze_Map_Editor|Waze Map Editor]] manual that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [[Philippines/Editing resources |Editing Resources for the Philippines]] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed on our guide are specifically for our pinoy roads and driving habits. ==I've been blocked and I can't edit on WME or send a report through the app== If you have received a message on the app or an email notification that you have been blocked, this is because of either 1. You have been detected by the Waze system as massively reporting. or 2. You have been reported by the community because you are violating the rules imposed by Waze and/or the community. If #1 is the case, even if we could, we will not help you with this. Like Waze, we do not tolerate cheating, and will not lift a finger to help you get unblocked or unbanned. By spamming the reports function you intentionally send out wrong, inconsistent, spurious, or unneeded data. You are also skewing the data being collected by Waze making the aggregate data inaccurate. If you fall under #2 then what you should do is 1. Read the wiki, particularly the [[Philippines]] section so you can figure out what you did wrong 2. Join the [https://www.facebook.com/groups/WazePhilippines/ Waze Philippines FB Group] 3. Join the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg Waze Philippines Telegram channel] 4. Post a message on the FB group or the Telegram channel and tell us your predicament. If you fail to read the wiki or figure out why you were blocked, we will not help you. ==Why am I not leveling up to Level 2 or 3?== We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]), have joined at least 1 [[Philippines/MapRaid_History|PH MapRaid]], have attended the "Intro to Map Editing Webinar", and have joined the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg PH Telegram channel]. This means all Waze editors will be force-ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. New Area Managers are also not automatically promoted to Level 3 and will remain at their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] ==How do I apply to be an Area Manager?== To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[global:Area_Manager|Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] ==How long does it take until my edits gets displayed on my Waze app?== It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area ==When I encounter traffic on the road, what type do I report?== You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph ==I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?== The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are '''NO ROADS''' which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, and most Expressways. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps because of report abuse. You will still be able to report them but they will no longer appear on WME and you will not get any points for them. ==What is the difference between Map Problems and Update Requests?== Map Problems or MPs are Waze generated and based on analyzed Wazer traffic. Update Requests or URs are Waze user submitted requests to fix user identified map issues. ==How do I fix Map Problems?== Visit the [[global:Map_Problems_in_Waze_Map_Editor|Map Problem]] wiki for more details. ==How do I fix Update Requests?== Visit the [[global:Update_Requests_in_Waze_Map_Editor|Update Requests]] wiki for more details. ==Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?== On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. ==Waze does not use the U-Turn segment I created between two roads, what could be the problem?== Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. ==Are there any shortcut keys for the Waze Map Editor?== You can view the wiki page on [[global:Keyboard_shortcuts|Keyboard shortcuts]] ==Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?== Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. ==I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?== You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. ==The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?== The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. ==There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?== You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the Partial[[global:Partial_restrictions| restrictions]] wiki. ==Search function doesn't work, how do I fix it?== This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. ==I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?== If refreshing the map editor does not work, go to [http://status.waze.com the Waze status page] and check for any announcement from Waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==How do I report flooding so that Wazers will not be routed on a flooded road?== Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report an unpassable road due to flooding, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank, and the country. *The road will be opened when Waze detects that a number of users have driven through the road. [[Category:Philippines]] 785a923aa8422f7cac3d3ea9ba4015c436531f75 10423 10407 2017-06-01T19:33:12Z Adabadada 39 /* Why am I not leveling up to Level 2 or 3? */ wikitext text/x-wiki __TOC__ *'''Here are the most asked questions from Pinoy Waze Editors''' ==Is there a manual for Waze map editing?== There is a [[global:Waze_Map_Editor|Waze Map Editor]] manual that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [[Philippines/Editing resources |Editing Resources for the Philippines]] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed on our guide are specifically for our pinoy roads and driving habits. ==I've been blocked and I can't edit on WME or send a report through the app== If you have received a message on the app or an email notification that you have been blocked, this is because of either 1. You have been detected by the Waze system as massively reporting. or 2. You have been reported by the community because you are violating the rules imposed by Waze and/or the community. If #1 is the case, even if we could, we will not help you with this. Like Waze, we do not tolerate cheating, and will not lift a finger to help you get unblocked or unbanned. By spamming the reports function you intentionally send out wrong, inconsistent, spurious, or unneeded data. You are also skewing the data being collected by Waze making the aggregate data inaccurate. If you fall under #2 then what you should do is 1. Read the wiki, particularly the [[Philippines]] section so you can figure out what you did wrong 2. Join the [https://www.facebook.com/groups/WazePhilippines/ Waze Philippines FB Group] 3. Join the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg Waze Philippines Telegram channel] 4. Post a message on the FB group or the Telegram channel and tell us your predicament. If you fail to read the wiki or figure out why you were blocked, we will not help you. ==Why am I not leveling up to Level 2 or 3?== We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]), have joined at least 1 [[Philippines/MapRaid_History|PH MapRaid]], have attended the "Intro to Map Editing Webinar", and have joined the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg PH Telegram channel]. This means all Waze editors will be force-ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. ''New Area Managers are also not automatically promoted to Level 3 and will remain at their level until the local champs agree to promote based on the quality of edits''. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] ==How do I apply to be an Area Manager?== To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[global:Area_Manager|Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] ==How long does it take until my edits gets displayed on my Waze app?== It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area ==When I encounter traffic on the road, what type do I report?== You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph ==I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?== The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are '''NO ROADS''' which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, and most Expressways. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps because of report abuse. You will still be able to report them but they will no longer appear on WME and you will not get any points for them. ==What is the difference between Map Problems and Update Requests?== Map Problems or MPs are Waze generated and based on analyzed Wazer traffic. Update Requests or URs are Waze user submitted requests to fix user identified map issues. ==How do I fix Map Problems?== Visit the [[global:Map_Problems_in_Waze_Map_Editor|Map Problem]] wiki for more details. ==How do I fix Update Requests?== Visit the [[global:Update_Requests_in_Waze_Map_Editor|Update Requests]] wiki for more details. ==Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?== On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. ==Waze does not use the U-Turn segment I created between two roads, what could be the problem?== Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. ==Are there any shortcut keys for the Waze Map Editor?== You can view the wiki page on [[global:Keyboard_shortcuts|Keyboard shortcuts]] ==Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?== Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. ==I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?== You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. ==The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?== The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. ==There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?== You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the Partial[[global:Partial_restrictions| restrictions]] wiki. ==Search function doesn't work, how do I fix it?== This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. ==I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?== If refreshing the map editor does not work, go to [http://status.waze.com the Waze status page] and check for any announcement from Waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==How do I report flooding so that Wazers will not be routed on a flooded road?== Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report an unpassable road due to flooding, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank, and the country. *The road will be opened when Waze detects that a number of users have driven through the road. [[Category:Philippines]] 68a0536ab8a500d0c89a53a0776b8ff9abcbc5df 0 8 10416 10276 2017-05-29T14:52:26Z Adabadada 39 Fixed link to Editing Manual wikitext text/x-wiki <!-- #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####----- #### This page has been curated #### #### to be included in the new #### #### Wazeopedia - GLOBAL Wiki. #### #### Please do not make any #### #### edits on this page without #### #### PRIOR CONSENSUS in the Wiki #### #### Updates and Discussions #### #### forum thread for this page. #### #### If a specific forum thread #### #### for this page doesn't exist #### #### please start one. #### #### www.waze.com/forum/ #### #### viewforum.php?f=276 #### #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--> * '''Read''' the topics on [http://support.google.com/waze Waze Help Center] * '''Get''' help when you have Waze running but the map shows few or no roads, or streets with no names, or you travel to an unmapped area * '''Understand''' the [[Timeline of updating process|timing of updates]], including when you can edit roads you have driven on * '''Edit''' ** ''Please do not'' edit the map until you have read the [[global:Waze_Map_Editor|Waze Map Editor]] manual and reviewed the [[best map editing practice]]s * '''Use''' the [[Dashboard|My Dashboard section on the Waze website]] * '''Read''' the [[FAQ|answers to Frequently Asked Questions (FAQ)]] and the [[glossary]] of terms * '''Participate''' in the [[Discussion Forums|announcements and discussion forums]] '''If you have problems''', try and find your own solution or ask the community for help: * Use the Wiki - there is a search box just to the left * Use the [[Discussion Forums]] '''If all else fails''', you can [[email Waze with your problem]] 37c253063f158de2b3562316eee7b0bed7edae18 10417 10416 2017-05-29T14:59:03Z Adabadada 39 Fixed links to Waze Map Editor manual and best map editing practices wikitext text/x-wiki <!-- #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####----- #### This page has been curated #### #### to be included in the new #### #### Wazeopedia - GLOBAL Wiki. #### #### Please do not make any #### #### edits on this page without #### #### PRIOR CONSENSUS in the Wiki #### #### Updates and Discussions #### #### forum thread for this page. #### #### If a specific forum thread #### #### for this page doesn't exist #### #### please start one. #### #### www.waze.com/forum/ #### #### viewforum.php?f=276 #### #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--> * '''Read''' the topics on [http://support.google.com/waze Waze Help Center] * '''Get''' help when you have Waze running but the map shows few or no roads, or streets with no names, or you travel to an unmapped area * '''Understand''' the [[Timeline of updating process|timing of updates]], including when you can edit roads you have driven on * '''Edit''' ** ''Please do not'' edit the map until you have read the [[global:Waze_Map_Editor|Waze Map Editor]] manual and reviewed the [[global:Best_map_editing_practice|best map editing practices]] * '''Use''' the [[Dashboard|My Dashboard section on the Waze website]] * '''Read''' the [[FAQ|answers to Frequently Asked Questions (FAQ)]] and the [[glossary]] of terms * '''Participate''' in the [[Discussion Forums|announcements and discussion forums]] '''If you have problems''', try and find your own solution or ask the community for help: * Use the Wiki - there is a search box just to the left * Use the [[Discussion Forums]] '''If all else fails''', you can [[email Waze with your problem]] 6ae1f8934bd0874bc5b94a7dc451f327c68de3c1 0 7 10431 10404 2017-06-18T08:45:24Z Kazmuth 35 /* Special Place Categories */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places), and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators though they also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :* When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination. :* When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do. :* Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map. :* When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app. :''<u>Placement of the navigation point:</u>'' :* Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. :* For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place. :* DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :* DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :* Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. These two don't always have to be separated, and it is perfectly acceptable to keep these joined as long as routing will remain correct and the point place is not too far from its actual location. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (he name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :Add the following information if it is known: :* Operator - The company that owns and operates the parking lot. :* Parking Lot Type: :*# Public - available for parking to general public without restriction. Does not matter what your destination is or whether or not there is a fee. :*# Restricted - available to general public under certain conditions. Any individual can park here as long as that individual is visiting this store, or this restaurant, or this shopping mall. You do not need a permit, any person can park there as long as that person meets certain conditions. Examples are stores, restaurants, shopping centers, some "visitor parking" lots (e.g., at an apartment complex or a university) :*# Private - available only to a select group of people. Only certain persons (e.g., residents of a certain condominium complex, workers in a certain office building, students at a particular university) can park there. You may need a permit to park there. :* Opening hours - hours of operation :* Number of spots :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== * For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. * For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' * For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). '''Example -''' Building A - Alphabet Estates * Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. '''Example''' Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie Name: D and E Enterprises ; Alternative Names: D & E Enterprises, D & E Ent., D and E Ent. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" and remove any slash (/) at the end * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * External Providers: Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 204056757549029ef2aac4df28aa1600c823dfab 10432 10431 2017-06-19T17:39:38Z Adabadada 39 /* EDITING PLACES */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that 1) will likely be a destination for driving and/or is a significant visual landmark, 2) is not a private residence, 3) is NOT a road (roads are already searchable on the app and it makes no sense to add them as places), and 4) actually exists ("sa puso mo" or "bahay ng duwende" will not work). The first thing to do when adding a new place is to make sure the location is correct. Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators though they also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :* When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination. :* When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do. :* Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map. :* When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app. :''<u>Placement of the navigation point:</u>'' :* Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. :* For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place. :* DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :* DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :* Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. These two don't always have to be separated, and it is perfectly acceptable to keep these joined as long as routing will remain correct and the point place is not too far from its actual location. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (the name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :Add the following information if it is known: :* Operator - The company that owns and operates the parking lot. :* Parking Lot Type: :*# Public - available for parking to general public without restriction. Does not matter what your destination is or whether or not there is a fee. :*# Restricted - available to general public under certain conditions. Any individual can park here as long as that individual is visiting this store, or this restaurant, or this shopping mall. You do not need a permit, any person can park there as long as that person meets certain conditions. Examples are stores, restaurants, shopping centers, some "visitor parking" lots (e.g., at an apartment complex or a university) :*# Private - available only to a select group of people. Only certain persons (e.g., residents of a certain condominium complex, workers in a certain office building, students at a particular university) can park there. You may need a permit to park there. :* Opening hours - hours of operation :* Number of spots :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== * For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. * For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' * For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). '''Example -''' Building A - Alphabet Estates * Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. '''Example''' Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie Name: D and E Enterprises ; Alternative Names: D & E Enterprises, D & E Ent., D and E Ent. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * Phone number format: +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * Website format: Remove "http://" or "https://" and remove any slash (/) at the end * Address: use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * External Providers: Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> DO NOT FORGET TO LOCK NEW PLACES TO LEVEL 4 (or the highest level available to you if you are below L4). <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 70c4a046f6d90ebb8aca60a6e6a3b86102e705c4 10449 10432 2017-06-21T13:57:09Z Adabadada 39 /* New Places */ Format change wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that: # will likely be a destination for driving and/or is a significant visual landmark, # is not a private residence # is NOT a road (roads are already searchable on the app and it makes no sense to add them as places) # actually exists ("sa puso mo" or "bahay ng duwende" will not work). Please follow the following guidelines when adding a New Place: # The first thing to do when adding a new place is to make sure the location is correct. # Then make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. # Next, determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). # Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). # Lastly, make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators though they also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :* When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination. :* When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do. :* Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map. :* When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app. :''<u>Placement of the navigation point:</u>'' :* Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. :* For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place. :* DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :* DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :* Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. These two don't always have to be separated, and it is perfectly acceptable to keep these joined as long as routing will remain correct and the point place is not too far from its actual location. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (the name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :Add the following information if it is known: :* Operator - The company that owns and operates the parking lot. :* Parking Lot Type: :*# Public - available for parking to general public without restriction. Does not matter what your destination is or whether or not there is a fee. :*# Restricted - available to general public under certain conditions. Any individual can park here as long as that individual is visiting this store, or this restaurant, or this shopping mall. You do not need a permit, any person can park there as long as that person meets certain conditions. Examples are stores, restaurants, shopping centers, some "visitor parking" lots (e.g., at an apartment complex or a university) :*# Private - available only to a select group of people. Only certain persons (e.g., residents of a certain condominium complex, workers in a certain office building, students at a particular university) can park there. You may need a permit to park there. :* Opening hours - hours of operation :* Number of spots :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== * Place names are very important because it affects search results. Make sure the name you use for a place will not only correctly identify the place but will not result in confusion for someone looking for it. * For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. * For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' * For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). '''Example -''' Building A - Alphabet Estates * Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. '''Example''' Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie Name: D and E Enterprises ; Alternative Names: D & E Enterprises, D & E Ent., D and E Ent. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * <u>Phone number format:</u> +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * <u>Website format:</u> Remove "http://" or "https://" and remove any slash (/) at the end * <u>Address:</u> use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * <u>External Providers:</u> Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> DO NOT FORGET TO LOCK NEW PLACES TO LEVEL 4 (or the highest level available to you if you are below L4). <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] b6ff8cc7ae3232cbdb4acf646d327f172b9384c2 10450 10449 2017-06-21T14:01:42Z Adabadada 39 /* New Places */ added how to determine if a place is a duplicate wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that: # will likely be a destination for driving and/or is a significant visual landmark, # is not a private residence # is NOT a road (roads are already searchable on the app and it makes no sense to add them as places) # actually exists ("sa puso mo" or "bahay ng duwende" will not work). Please follow the following steps/guidelines when adding a New Place: # The first thing to do when adding a new place is to make sure the location is correct. # Make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. #* In determining if a new place is a duplicate, you may need to #** Manually examine existing places in the area #** Use the WME search bar. Sometimes you will find that the place is already registered in the Waze map. # Determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). # Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). # Make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators though they also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :* When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination. :* When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do. :* Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map. :* When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app. :''<u>Placement of the navigation point:</u>'' :* Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. :* For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place. :* DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :* DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :* Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. These two don't always have to be separated, and it is perfectly acceptable to keep these joined as long as routing will remain correct and the point place is not too far from its actual location. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (the name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :Add the following information if it is known: :* Operator - The company that owns and operates the parking lot. :* Parking Lot Type: :*# Public - available for parking to general public without restriction. Does not matter what your destination is or whether or not there is a fee. :*# Restricted - available to general public under certain conditions. Any individual can park here as long as that individual is visiting this store, or this restaurant, or this shopping mall. You do not need a permit, any person can park there as long as that person meets certain conditions. Examples are stores, restaurants, shopping centers, some "visitor parking" lots (e.g., at an apartment complex or a university) :*# Private - available only to a select group of people. Only certain persons (e.g., residents of a certain condominium complex, workers in a certain office building, students at a particular university) can park there. You may need a permit to park there. :* Opening hours - hours of operation :* Number of spots :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== * Place names are very important because it affects search results. Make sure the name you use for a place will not only correctly identify the place but will not result in confusion for someone looking for it. * For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. * For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' * For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). '''Example -''' Building A - Alphabet Estates * Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. '''Example''' Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie Name: D and E Enterprises ; Alternative Names: D & E Enterprises, D & E Ent., D and E Ent. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * <u>Phone number format:</u> +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * <u>Website format:</u> Remove "http://" or "https://" and remove any slash (/) at the end * <u>Address:</u> use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * <u>External Providers:</u> Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> DO NOT FORGET TO LOCK NEW PLACES TO LEVEL 4 (or the highest level available to you if you are below L4). <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 993345d24576f6b0b125249d5bf704d912a52451 10451 10450 2017-06-21T14:09:31Z Adabadada 39 /* Reviewing "New Place" Reports */ Added General Guidelines fro all PURs wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that: # will likely be a destination for driving and/or is a significant visual landmark, # is not a private residence # is NOT a road (roads are already searchable on the app and it makes no sense to add them as places) # actually exists ("sa puso mo" or "bahay ng duwende" will not work). Please follow the following steps/guidelines when adding a New Place: # The first thing to do when adding a new place is to make sure the location is correct. # Make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place. #* In determining if a new place is a duplicate, you may need to #** Manually examine existing places in the area #** Use the WME search bar. Sometimes you will find that the place is already registered in the Waze map. # Determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories). # Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted). # Make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile. ==== Place Types ==== :'''Area Places''' - These are primarily POI locators though they also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :* When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination. :* When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do. :* Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map. :* When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app. :''<u>Placement of the navigation point:</u>'' :* Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. :* For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place. :* DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :* DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :* Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. These two don't always have to be separated, and it is perfectly acceptable to keep these joined as long as routing will remain correct and the point place is not too far from its actual location. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (the name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :Add the following information if it is known: :* Operator - The company that owns and operates the parking lot. :* Parking Lot Type: :*# Public - available for parking to general public without restriction. Does not matter what your destination is or whether or not there is a fee. :*# Restricted - available to general public under certain conditions. Any individual can park here as long as that individual is visiting this store, or this restaurant, or this shopping mall. You do not need a permit, any person can park there as long as that person meets certain conditions. Examples are stores, restaurants, shopping centers, some "visitor parking" lots (e.g., at an apartment complex or a university) :*# Private - available only to a select group of people. Only certain persons (e.g., residents of a certain condominium complex, workers in a certain office building, students at a particular university) can park there. You may need a permit to park there. :* Opening hours - hours of operation :* Number of spots :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== * Place names are very important because it affects search results. Make sure the name you use for a place will not only correctly identify the place but will not result in confusion for someone looking for it. * For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. * For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' * For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). '''Example -''' Building A - Alphabet Estates * Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. '''Example''' Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie Name: D and E Enterprises ; Alternative Names: D & E Enterprises, D & E Ent., D and E Ent. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * <u>Phone number format:</u> +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * <u>Website format:</u> Remove "http://" or "https://" and remove any slash (/) at the end * <u>Address:</u> use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * <u>External Providers:</u> Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== General Guidelines for all PURs ==== Before approving a New Place or PUR, it is good practice to: # Google the establishment to confirm if it really exists and acquire more details from the websites # Use the WME/Google Street View to confirm the exact location of the establishment. It should be noted that the images may not be up to date but there may be familiar structures that can help you determine the correct location. This is particularly helpful if the PUR has a photo of the establishment. ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> DO NOT FORGET TO LOCK NEW PLACES TO LEVEL 4 (or the highest level available to you if you are below L4). <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 0baeada9fb2c23d4b3431e2c61c71c9497a7e63e 10452 10451 2017-06-21T14:24:33Z Adabadada 39 wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that: #<blockquote>will likely be a destination for driving and/or is a significant visual landmark,</blockquote> #<blockquote>is not a private residence</blockquote> #<blockquote>is NOT a road (roads are already searchable on the app and it makes no sense to add them as places)</blockquote> #<blockquote>actually exists ("sa puso mo" or "bahay ng duwende" will not work).</blockquote> Please follow the following steps/guidelines when adding a New Place: #<blockquote>The first thing to do when adding a new place is to make sure the location is correct.</blockquote> #<blockquote>Make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place.</blockquote> #*<blockquote>In determining if a new place is a duplicate, you may need to</blockquote> #**<blockquote>Manually examine existing places in the area</blockquote> #**<blockquote>Use the WME search bar. Sometimes you will find that the place is already registered in the Waze map.</blockquote> #<blockquote>Determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories).</blockquote> #<blockquote>Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted).</blockquote> #<blockquote>Make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile.</blockquote> ==== Place Types ==== :'''Area Places''' - These are primarily POI locators though they also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :* When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination. :* When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do. :* Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map. :* When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app. :''<u>Placement of the navigation point:</u>'' :* Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. :* For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place. :* DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :* DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :* Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. These two don't always have to be separated, and it is perfectly acceptable to keep these joined as long as routing will remain correct and the point place is not too far from its actual location. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (the name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :Add the following information if it is known: :* Operator - The company that owns and operates the parking lot. :* Parking Lot Type: :*# Public - available for parking to general public without restriction. Does not matter what your destination is or whether or not there is a fee. :*# Restricted - available to general public under certain conditions. Any individual can park here as long as that individual is visiting this store, or this restaurant, or this shopping mall. You do not need a permit, any person can park there as long as that person meets certain conditions. Examples are stores, restaurants, shopping centers, some "visitor parking" lots (e.g., at an apartment complex or a university) :*# Private - available only to a select group of people. Only certain persons (e.g., residents of a certain condominium complex, workers in a certain office building, students at a particular university) can park there. You may need a permit to park there. :* Opening hours - hours of operation :* Number of spots :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== * Place names are very important because it affects search results. Make sure the name you use for a place will not only correctly identify the place but will not result in confusion for someone looking for it. * For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms. * For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name. ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' * For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). '''Example -''' Building A - Alphabet Estates * Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place. '''Example''' Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie Name: D and E Enterprises ; Alternative Names: D & E Enterprises, D & E Ent., D and E Ent. ==== Other Place Details ==== * Put only verified services and operating times. Leave blank if unsure * <u>Phone number format:</u> +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes) * <u>Website format:</u> Remove "http://" or "https://" and remove any slash (/) at the end * <u>Address:</u> use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format. * <u>External Providers:</u> Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher] === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== General Guidelines for all PURs ==== Before approving a New Place or PUR, it is good practice to: # Google the establishment to confirm if it really exists and acquire more details from the websites # Use the WME/Google Street View to confirm the exact location of the establishment. It should be noted that the images may not be up to date but there may be familiar structures that can help you determine the correct location. This is particularly helpful if the PUR has a photo of the establishment. ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> DO NOT FORGET TO LOCK NEW PLACES TO LEVEL 4 (or the highest level available to you if you are below L4). <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] c1eaee5b51d3799b2ca429a08d9efc3cd101e237 10453 10452 2017-06-21T14:32:20Z Adabadada 39 /* New Places */ format wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that: #<blockquote>will likely be a destination for driving and/or is a significant visual landmark,</blockquote> #<blockquote>is not a private residence</blockquote> #<blockquote>is NOT a road (roads are already searchable on the app and it makes no sense to add them as places)</blockquote> #<blockquote>actually exists ("sa puso mo" or "bahay ng duwende" will not work).</blockquote> Please follow the following steps/guidelines when adding a New Place: #<blockquote>The first thing to do when adding a new place is to make sure the location is correct.</blockquote> #<blockquote>Make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place.</blockquote> #*<blockquote>In determining if a new place is a duplicate, you may need to</blockquote> #**<blockquote>Manually examine existing places in the area</blockquote> #**<blockquote>Use the WME search bar. Sometimes you will find that the place is already registered in the Waze map.</blockquote> #<blockquote>Determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories).</blockquote> #<blockquote>Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted).</blockquote> #<blockquote>Make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile.</blockquote> ==== Place Types ==== :'''Area Places''' - These are primarily POI locators though they also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :* When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination. :* When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do. :* Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map. :* When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app. :''<u>Placement of the navigation point:</u>'' :* Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point. :* For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place. :* DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason. :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :* DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. :* Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. These two don't always have to be separated, and it is perfectly acceptable to keep these joined as long as routing will remain correct and the point place is not too far from its actual location. ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (the name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :Add the following information if it is known: :* Operator - The company that owns and operates the parking lot. :* Parking Lot Type: :*# Public - available for parking to general public without restriction. Does not matter what your destination is or whether or not there is a fee. :*# Restricted - available to general public under certain conditions. Any individual can park here as long as that individual is visiting this store, or this restaurant, or this shopping mall. You do not need a permit, any person can park there as long as that person meets certain conditions. Examples are stores, restaurants, shopping centers, some "visitor parking" lots (e.g., at an apartment complex or a university) :*# Private - available only to a select group of people. Only certain persons (e.g., residents of a certain condominium complex, workers in a certain office building, students at a particular university) can park there. You may need a permit to park there. :* Opening hours - hours of operation :* Number of spots :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== *<blockquote>Place names are very important because it affects search results. Make sure the name you use for a place will not only correctly identify the place but will not result in confusion for someone looking for it.</blockquote> *<blockquote>For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms.</blockquote> *<blockquote>For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name.</blockquote> ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' *<blockquote>For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). '''Example -''' Building A - Alphabet Estates</blockquote> *<blockquote>Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place.</blockquote> <blockquote>'''Example'''</blockquote><blockquote>Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie</blockquote><blockquote>Name: D and E Enterprises ; Alternative Names: D & E Enterprises, D & E Ent., D and E Ent.</blockquote> ==== Other Place Details ==== *<blockquote>Put only verified services and operating times. Leave blank if unsure</blockquote> *<blockquote><u>Phone number format:</u> +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes)</blockquote> *<blockquote><u>Website format:</u> Remove "http://" or "https://" and remove any slash (/) at the end</blockquote> *<blockquote><u>Address:</u> use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format.</blockquote> *<blockquote><u>External Providers:</u> Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher]</blockquote> === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== General Guidelines for all PURs ==== Before approving a New Place or PUR, it is good practice to: #<blockquote>Google the establishment to confirm if it really exists and acquire more details from the websites</blockquote> #<blockquote>Use the WME/Google Street View to confirm the exact location of the establishment. It should be noted that the images may not be up to date but there may be familiar structures that can help you determine the correct location. This is particularly helpful if the PUR has a photo of the establishment.</blockquote> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> DO NOT FORGET TO LOCK NEW PLACES TO LEVEL 4 (or the highest level available to you if you are below L4). <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 32f0d57a8a089771a95d19bfd239546bbcc6e5a9 10454 10453 2017-06-21T14:35:41Z Adabadada 39 /* Philippine Places Policy */ wikitext text/x-wiki __TOC__ ==Philippine Places Policy== *'''Introduction''' This will serve as a guide for Waze Philippines on how to edit places and what should be approved and rejected for Place Update submissions. The community has come up with very specific standards for the classification and naming of places. All editors who want to edit places in the Philippines are asked to observe the following standards very carefully. At present verified places are locked to at least Level 4 to ensure that all edits will be reviewed by a local champ. === '''<u>EDITING PLACES</u>''' === ==== New Places ==== Before anything else, decide whether a place has to be on the WME at all. We only add a location that: #<blockquote>will likely be a destination for driving and/or is a significant visual landmark,</blockquote> #<blockquote>is not a private residence</blockquote> #<blockquote>is NOT a road (roads are already searchable on the app and it makes no sense to add them as places)</blockquote> #<blockquote>actually exists ("sa puso mo" or "bahay ng duwende" will not work).</blockquote> Please follow the following steps/guidelines when adding a New Place: #<blockquote>The first thing to do when adding a new place is to make sure the location is correct.</blockquote> #<blockquote>Make sure the contemplated place will not be a duplicate of another place on the WME, be it an Area Place or a Point Place.</blockquote> #*<blockquote>In determining if a new place is a duplicate, you may need to</blockquote> #**<blockquote>Manually examine existing places in the area</blockquote> #**<blockquote>Use the WME search bar. Sometimes you will find that the place is already registered in the Waze map.</blockquote> #<blockquote>Determine whether it should be an Area Place or Point Place (see guidelines for place type), then choose the appropriate category (see place categories).</blockquote> #<blockquote>Once you've added a place you must then add all the pertinent details. At the minimum you should put the Name and Address. Unnamed places are useless for navigation and are not searchable on the app. As for place addresses, remember to remove the DPWH RNS number from the street name, and make sure the house number is purely numeric (letters will not be accepted).</blockquote> #<blockquote>Make sure the navigation point (if an area place) or the point place are placed right where the Wazer is supposed to be notified that they've arrived. If an Area Place will go beyond a city's/municipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile.</blockquote> ==== Place Types ==== :'''Area Places''' - These are primarily POI locators though they also serve another function on the Waze map. They serve as '''navigation aids and visual cues'''. So if a place is a significant landmark (serves as a navigation cue) and is more than '''50m on its X or Y coordinates''', you can use this place type. If it is smaller than 50m, consider adding a Point Place instead. Compounds and buildings fall under this place type. :''<u>Pointers for using Area Places:</u>'' :*<blockquote>When drawing an Area Place make sure to include the entire place ''including its parking lot''. Draw it right up to its fences/walls. The parking lot then has to be drawn as another Area Place within the bigger establishment. The bigger place will appear as a gray polygon in the app while the parking lot will appear as a blue polygon that will only appear as the Wazer is approaching the destination.</blockquote> :*<blockquote>When drawing an area place, be very conscious of parallax, especially for very tall buildings. Don't just simply trace the entire building, as that will result in a misrepresentation of the actual location of the building. Try to trace the base of the building instead. A helpful technique, though not applicable to all, is to trace the rooftop of the building first and then move it to the base of the building. As with all Area Places, do not forget to move the navigation point to the correct location. On a related note, try to draw the simplest shape for the building - no need to trace the intricacies of a building when a simple rectangle/square/other basic polygon will do.</blockquote> :*<blockquote>Try to avoid drawing an Area Place within an Area Place. This will not display properly on the client and will only appear as one whole gray area. The only exception is if it is essential for navigation that the name of the smaller place appears on the map.</blockquote> :*<blockquote>When drawing adjacent Area Places, do not let their borders overlap or touch each other. Always leave some space between the two, otherwise it will render as a contiguous sea of gray on the app.</blockquote> :''<u>Placement of the navigation point:</u>'' :*<blockquote>Leave the navigation point at the location where the Wazer should be informed that he/she has arrived, relative to the road. Keep in mind that the client will route the driver to the road segment nearest to the navigation point.</blockquote> :*<blockquote>For places with multiple entrances, try to locate the main entrance and use that. For places with in-building parking, DON'T leave the navigation point at the parking entrance. Instead, draw another area place for the parking and use that place's navigation point to indicate the parking entrance. The driver will be routed to the main entrance/lobby but will also be shown the entrance to the parking lot as he/she approaches the place.</blockquote> :*<blockquote>DO NOT leave the navigation point right on top of a road segment, and especially not on top of a node - this can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on. Try to avoid placing geometry nodes on top of segments for the same reason.</blockquote> :'''Point Places''' - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app but not visible on the map unless selected as a destination. If there is already an Area Place, do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type. :''<u>Placement of point places:</u>'' :*<blockquote>DO NOT leave a point place and/or its navigation point right on top of a road segment, and especially not on top of a node. This can make it difficult to edit. Leave it off to the side of the segment, as this will also serve as a visual cue to the Wazer as to which side of the road the establishment is on.</blockquote> :*<blockquote>Put the Point Place at the actual location of the establishment and put the navigation point adjacent to the nearest road segment to which the Wazer should be guided. These two don't always have to be separated, and it is perfectly acceptable to keep these joined as long as routing will remain correct and the point place is not too far from its actual location.</blockquote> ==== Special Place Categories ==== :'''Gas Station''' - Gas stations should always be mapped as Area Places. If the X or Y coordinate of the contemplated place is not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length. This is so that it will get displayed on the client app. :- Please note NOT to use "Others" for gas station brand as this can cause issues with categorial search results (the name of the gas station gets displayed as "Others" instead of the actual name of the gas station). :'''Parking Lot''' - All parking lots should be mapped as Area Places. Once added to the WME, Parking Lot categories cannot be changed so be very careful about using this category or approving PURs using this category. Trace the parking lot as an area and place the navigation point at the entrance. Use the establishment's name followed by "Parking" or "Carpark" when naming. For parking lots with no official name or are not associated with an establishment, don't leave them unnamed. Use "Parking Lot" as its name instead. :Add the following information if it is known: :* Operator - The company that owns and operates the parking lot. :* Parking Lot Type: :*# Public - available for parking to general public without restriction. Does not matter what your destination is or whether or not there is a fee. :*# Restricted - available to general public under certain conditions. Any individual can park here as long as that individual is visiting this store, or this restaurant, or this shopping mall. You do not need a permit, any person can park there as long as that person meets certain conditions. Examples are stores, restaurants, shopping centers, some "visitor parking" lots (e.g., at an apartment complex or a university) :*# Private - available only to a select group of people. Only certain persons (e.g., residents of a certain condominium complex, workers in a certain office building, students at a particular university) can park there. You may need a permit to park there. :* Opening hours - hours of operation :* Number of spots :'''Hospital/Urgent Care''' - Only places that offer emergency medical services may use this category. Other medical/paramedical facilities must be categorized as Doctor/Clinic or Offices. :'''Residence/Home''' - This category is no longer an option in the drop-down menu on the WME but is still in use for some old places. At present this category can only be added by Wazers using the client. These are private residences that will not be searchable on the client app. The names of old places that used this category have been automatically removed. If you see any public place using this category, choose a more appropriate category and rename it. Only private residences should use this category. If it has been mapped correctly it should appear as a triangular point place. Area Places using this category are incorrect. : :Refer to the [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Places_Policy Places Policy] for more details on what can be added. ==== Naming Places ==== *<blockquote>Place names are very important because it affects search results. Make sure the name you use for a place will not only correctly identify the place but will not result in confusion for someone looking for it.</blockquote> *<blockquote>For most places, use the name on the signage as the primary name and then add alternative names for other commonly-known names for the establishment. Observe proper capitalization: ''we use Title Case for all place names'' regardless of how it is written on the signage, though we make an exception for acronyms.</blockquote> *<blockquote>For businesses with multiple franchises make sure to put a branch name/locator after the business name, following this format: '''<Business Name> - <Branch/Locator>'''. This is to prevent getting multiple generic names when a Wazer is searching for a specific branch. When deciding what branch name to put consider what a Wazer will likely use as a search term. This is of particular importance for gas stations whose branch names are often not known by customers and are instead known for their location. In those cases we use the location as the branch name.</blockquote> ''*Please note the dash between the business name and branch name. The exceptions to this format are Banks and other places that already have dashes (not hyphens) in their names.'' *<blockquote>For a place-within-a-place (e.g. condominium buildings within a larger development, business establishments within a mall, school buildings within a larger school compound, etc.), put the name of the building/establishment first, followed by the name of the larger place (separated by a dash). '''Example -''' Building A - Alphabet Estates</blockquote> *<blockquote>Use the "Alternative Names" to add other possible iterations of the name that you think an ordinary Wazer might use to search for the place.</blockquote> <blockquote>'''Example'''</blockquote><blockquote>Name: ABC ; Alternative Names: Alpha Beta Charlie, AlphaBetaCharlie</blockquote><blockquote>Name: D and E Enterprises ; Alternative Names: D & E Enterprises, D & E Ent., D and E Ent.</blockquote> ==== Other Place Details ==== *<blockquote>Put only verified services and operating times. Leave blank if unsure</blockquote> *<blockquote><u>Phone number format:</u> +63 (Area Code) XXX XXXX OR +63AreaCode XXX XXXX (no dashes)</blockquote> *<blockquote><u>Website format:</u> Remove "http://" or "https://" and remove any slash (/) at the end</blockquote> *<blockquote><u>Address:</u> use the establishment's listed address whenever possible. Do not use the DPWH RNS, and do not just copy the Waze road name (e.g. avoid using 1: EDSA S or 1: EDSA W, just use EDSA). Some wazers mistakenly use the house number field for the phone number. Please correct accordingly. As of this writing, only numeric house numbers are accepted. Do not accept alphanumeric house numbers, particularly those that use the Block and Lot number format.</blockquote> *<blockquote><u>External Providers:</u> Sometimes Waze uses third-party results for places, and unfortunately, many of these third-party results are wrong. Use this feature to link Google Maps results to Waze places so that even if the user selects the Google result, they will still be routed to the Waze place. When this feature was launched, places were auto-linked to Google Maps. It still happens for new places that we add to the map. Always check if the auto-linked places are correct. You can also manually link/unlink places.. [This feature is available only to editors level 3 or higher]</blockquote> === '''<u>HANDLING PLACE UPDATE REQUESTS</u>''' === Place Update Requests (PURs) are place reports sent from the client app. There are four kinds of PURs: New Place, New Picture, New details for place, and Flag requests. Every report that gets approved counts toward a user becoming trusted. A trusted user's submissions will no longer have to be reviewed before appearing on the app. This is why we are very strict about approving reports - we don't want careless people to become trusted users. On the other hand, any user can be distrusted if they submit a certain number of PURs that have been rejected. However, regardless of trusted/distrusted status, users can get blacklisted and banned from adding places if they have enough submissions that get flagged. We also track places that have to be removed - if we see a pattern where a certain user created many of these, he could get blacklisted.<br /> ==== General Guidelines for all PURs ==== Before approving a New Place or PUR, it is good practice to: #<blockquote>Google the establishment to confirm if it really exists and acquire more details from the websites</blockquote> #<blockquote>Use the WME/Google Street View to confirm the exact location of the establishment. It should be noted that the images may not be up to date but there may be familiar structures that can help you determine the correct location. This is particularly helpful if the PUR has a photo of the establishment.</blockquote> ==== Reviewing "New Place" Reports ==== There are two kinds of "New Place" reports - reports for public places and Residence/Home. For "New place" PURs for public places, apply the same standard for creating new places on the WME. That is, determine first if it even needs to be on the WME and make sure it is in the correct location before approving. Once you approve a new place, edit it further to make sure it fits our standards for places (above). If you have to move the location, change the category, place type, etc, do so. Delete inappropriate pictures if there are any. For "New place" PURs under the Residence/Home category, approve only places with a valid address (house number required). Make sure the location is correct. Once done, edit the road segment adjacent to the place and add the street number to the segment. '''Approve''' *New places that are legitimate POIs. Confirm if it is a real place and at the correct location. *New places marked as Residence/Home WITH Address (Street number and Street) '''Reject'''<br /> *Place submissions for roads/streets - check if the adjacent segment is correctly named, reject the PUR. *Duplicate places - If the new place contains more information or detail than the existing place, copy these information over to the old place and then reject the new place submission. *Inappropriate places - bored Wazers submit all sorts of things as places: traffic, trees, dirty fingers, cuss words, etc. Report these places to a local champ so the erring reporter can be dealt with accordingly. *Incorrect capitalization and spelling - create new place instead and reject UR.* *Incorrect information* <nowiki>*</nowiki>Why not just approve the place and manually correct the capitalization/spelling/information? If a reporter gets a certain number of reports approved, he/she eventually becomes a trusted user and their submissions will no longer need to be reviewed before appearing on the app. We don't want someone careless to become a trusted user so reject these reports.<br /> DO NOT FORGET TO LOCK NEW PLACES TO LEVEL 4 (or the highest level available to you if you are below L4). <br /> ==== Reviewing Pictures<br /> ==== In reviewing pictures, put yourself in the shoes of someone who will be going to that place and does not know where to go or what to look for. The picture should be something that will make it easier for anyone to find that place. '''Approve''' *Clear image of entrance/facade *Clear image of building or structure *Images including a signage / billboard of the establishment displaying its name &/or address *House or residence images set to private viewing - that is, approve only for places classified as Residence/Home '''Reject''' *House or residence images set to public viewing - that is, places not classified as Residence/Home *Obstructed view or taken while inside a vehicle *Images with faces *Dark images *Blurred images *Images with clear plate number or conduction sticker of vehicles *Interior images of buildings *Images showing incorrect place *Pornographic images or other inappropriate pictures *Blank/Green image - the reporter encountered problems uploading the photo <br /> ==== Reviewing "New Details for Place" Reports <br /> ==== Accept only updates that are correct. Again, we do not want careless or malicious people to become trusted users. If there are just minor formatting issues, that is fine to approve, otherwise reject all submissions that do not conform to our standards above. Pay special attention to services offered, as many Wazers like to add multiple services even if the establishment does not offer it, just to get extra points. Also be very wary of requests to edit the location/navigation point, as many users like to move this to their residence. Some like to hijack an existing place to add the details of another place instead of creating a New Place request. Many also like changing the name of a public place to "Home" or "X's Residence." Needless to say, be careful in approving new details for any place. '''Adding place addresses'''<br />See guidelines for addresses above. DO NOT add the RNS route numbers or blindly copy the Waze road name. Use just the official street names. '''Approve''' *Correct information '''Reject''' *Wrong information *Wrong capitalization ==== Reviewing Flag Requests ==== Be careful about approving flag requests because depending on the what the place was flagged for, selecting "solved" results in different consequences. At the same time, a Wazer whose submissions get flagged enough times can get banned from submitting PURs. This would be fine if we didn't have other Wazers who abuse the flag function but some people just flag stuff for no reason. '''Flag reasons and appropiate actions to take''' Closed or moved - select "delete place" only if you are sure the place is closed and will not re-open. Some places close temporarily, for renovations or other reasons. Duplicate - DO NOT choose to merge places even if they are duplicates. Previous attempts at merging places have resulted in both places becoming unusable. Instead, select "ignore flag", choose to retain the older place, copy pertinent details from the newer place to the older place, make sure all details are correct for the place that will be retained, and then delete the newer place. Inappropriate place - selecting "solved" will result in the place getting deleted. Do this only if you are sure the place does not belong on the map. Residential place - selecting "solved" will result in the place getting re-categorized as a Residence/Home. Places under this category lose their name and become unsearchable on the app. Such flags should only be approved for private residences. The following DO NOT qualify as private residences: Condominiums, villages/subdivisions, barangays, and any other place where the public is allowed. Wrong details - select "solved" only if the details were actually wrong. Otherwise, select "ignore flag". Some people like flagging gas stations for having the wrong prices. Ignore those flags. Picture - choose to delete pictures only if they violate our standards. [[Category:Philippines]] 2b93e4f06fbef69b2b6e346f121a0a7e7a7e75e8 0 1 10433 10428 2017-06-19T17:45:55Z Adabadada 39 /* New to Editing? Start Here */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 6fd2f10c7d9ca03791ec5478a9614227c4d42c7b 10435 10433 2017-06-19T18:00:26Z Adabadada 39 Moved around some links to different subheadings wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 9ad9076f05cd1974f52618605de0c3de0a94d9f3 10436 10435 2017-06-19T18:01:25Z Adabadada 39 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * Meetups * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 36d832c32e02a7bbe67685c864c5d2e12bfab135 10437 10436 2017-06-19T18:03:53Z Adabadada 39 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [https://wiki.waze.com/wiki/Philippines/Editing_resources#Philippine_Waze_Area_Manager Philippines Area Managers], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * Meetups * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 6c8c1490bfd5a48ee15f0e2568541fe0903ffc5e 10438 10437 2017-06-19T18:07:26Z Adabadada 39 /* External Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines and Resources for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [[Philippines/Champs And AMs|Philippines Area Managers]], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * Meetups * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] af10a5973ed0be0a57310e7ea7d8d67d5751b245 10439 10438 2017-06-19T18:11:47Z Adabadada 39 /* Editing Guidelines and Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [[Philippines/Champs And AMs|Philippines Area Managers]], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * Meetups * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 1a754e9c9a18132250862967469804f336dfd7c8 10440 10439 2017-06-19T18:14:41Z Adabadada 39 /* New to Editing? Start Here */ added link to WME Manual wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[:uk:Quick_Start|Quick Start]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] * [[global:Waze_Map_Editor|Waze Map Editor Manual]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [[Philippines/Champs And AMs|Philippines Area Managers]], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * Meetups * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 90cce37c0d3845e3cc94152df4eca9d4bedfc34b 10443 10440 2017-06-19T19:18:06Z Adabadada 39 /* New to Editing? Start Here */ Removed Quick Start wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * [[Philippines/Places_Policy |Places_Policy ]] Guidelines for editing places and handling Place Update Requests * [[Philippines/Update_Requests |Update_Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [[Philippines/Champs And AMs|Philippines Area Managers]], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * Meetups * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] ad12d9a31cb30ad7df06e2250ca01d3ce757f073 10444 10443 2017-06-19T19:21:23Z Adabadada 39 /* Getting Started */ Added new topics to be written in the future wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [[Philippines/Champs And AMs|Philippines Area Managers]], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are enjoined to join the community. Those who refuse to join have no chance to become a trusted editor. The primary means of communication of the editing community is Telegram although we also have non-editors in the group. * [[Self-management statement]] * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * Meetups * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] b931f0fa2fe1ac92622f98b5c8affb47a0ec5d90 10445 10444 2017-06-20T07:57:35Z Adabadada 39 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [[Philippines/Champs And AMs|Philippines Area Managers]], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * [[Self-management statement]] * [[Philippines/Champs_And_AMs |Champs_And_AMs ]] Meet the PH Global and Local Champs and the Area Managers * Meetups * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 29c43e4425c84dff9f978ac7a6d545e709d0f69a 10448 10445 2017-06-21T09:02:08Z Adabadada 39 /* About Waze */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [[Philippines/Champs And AMs|Philippines Area Managers]], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * Meetups * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 24dd1a6c0e058638681811062573402cffcf88b8 10455 10448 2017-06-22T06:06:21Z Adabadada 39 /* External Editing Resources for the Philippines */ Added link to new page - Meetups wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [[Philippines/Champs And AMs|Philippines Area Managers]], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 765aeb40b44e378376ebc438d595262a1ccf5e0c 10474 10455 2017-07-10T02:25:27Z Kazmuth 35 /* External Editing Resources for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed here [[Philippines/Champs And AMs|Philippines Area Managers]], you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] ed290741383d498ba88c4f4b0691254397e7f012 10475 10474 2017-07-10T02:28:17Z Kazmuth 35 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://telegram.me/joinchat/AgCmlwCFY_KGrMsMFv74Kg Philippine Wazers' Telegram chat group] [[Category:Philippines]] ed46c02cd41b6498b2788c399ff2467e67d6c7af 10478 10475 2017-08-09T05:01:36Z Kazmuth 35 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == (This section under construction for the PH. Links to other Local Pages for now) * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3Q_LenyNej5Fg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 886824bf8f6c436905c59665aa70ef6559cf56cd 0 9 10434 10307 2017-06-19T17:50:52Z Adabadada 39 wikitext text/x-wiki <!-- This page is transcluded into the main page and possibly other pages -->Waze is a free navigation app for your GPS equipped smartphone. It has the following features: * Spoken turn-by-turn directions * Spoken street names (Text-to-Speech) {{ref label|a|a}} * Real time traffic reports * Real time Gas Prices {{ref label|b|b}} * Toll road avoidance {{ref label|b|b}} * Free regular updates to the map that [[improve and edit the maps| you can help make]] are installed automatically * Search for destinations how you like: entire address at once, category, place name, landmark or use the addresses from your contacts * Integrated destination search: Google, Foursquare, Bing * Support for apps to insert destinations into Waze, such as Localscope * Support for multiple [[Countries and Languages| languages]] * Gaming elements for fun and integrated [[social networking]] <small>{{note|a|a}} BETA: in selected countries<br/> {{note|b|b}} Toll Roads and Gas Prices dependent on user contribution</small> Read more about the amazing way Waze gets better when you [[global:Just_drive_around_with_Waze_turned_on|just drive around with Waze turned on]] <noinclude><!-- prevents the pages receiving this page from picking up this category --> [[Category:Transcludable pages]] </noinclude> e83cd6fdd7d01947fbb930cbe46107bd23840431 10441 10434 2017-06-19T18:59:44Z Adabadada 39 Fixed broken links wikitext text/x-wiki <!-- This page is transcluded into the main page and possibly other pages -->Waze is a free navigation app for your GPS equipped smartphone. It has the following features: * Spoken turn-by-turn directions * Spoken street names (Text-to-Speech) {{ref label|a|a}} * Real time traffic reports * Real time Gas Prices {{ref label|b|b}} * Toll road avoidance {{ref label|b|b}} * Free regular updates to the map that [[global:Improve_and_edit_the_maps| you can help make]] are installed automatically * Search for destinations how you like: entire address at once, category, place name, landmark or use the addresses from your contacts * Integrated destination search: Google, Foursquare, Bing * Support for apps to insert destinations into Waze, such as Localscope * Support for multiple [[global:Countries_and_Languages| languages]] * Gaming elements for fun and integrated [[global:Social_networking|social networking]] <small>{{note|a|a}} BETA: in selected countries<br/> {{note|b|b}} Toll Roads and Gas Prices dependent on user contribution</small> Read more about the amazing way Waze gets better when you [[global:Just_drive_around_with_Waze_turned_on|just drive around with Waze turned on]] <noinclude><!-- prevents the pages receiving this page from picking up this category --> [[Category:Transcludable pages]] </noinclude> cbb9417af45ff2fae816405be3d5e5a27147dd16 0 8 10442 10417 2017-06-19T19:12:06Z Adabadada 39 Links wikitext text/x-wiki <!-- #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####----- #### This page has been curated #### #### to be included in the new #### #### Wazeopedia - GLOBAL Wiki. #### #### Please do not make any #### #### edits on this page without #### #### PRIOR CONSENSUS in the Wiki #### #### Updates and Discussions #### #### forum thread for this page. #### #### If a specific forum thread #### #### for this page doesn't exist #### #### please start one. #### #### www.waze.com/forum/ #### #### viewforum.php?f=276 #### #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--> * '''Read''' the topics on [http://support.google.com/waze Waze Help Center] * '''Get''' help when you have Waze running but the map shows few or no roads, or streets with no names, or you travel to an unmapped area * '''Understand''' the [[global:Timeline_of_updating_process|timing of updates]], including when you can edit roads you have driven on * '''Edit''' ** ''Please do not'' edit the map until you have read the [[global:Waze_Map_Editor|Waze Map Editor]] manual and reviewed the [[global:Best_map_editing_practice|best map editing practices]] * '''Use''' the [https://www.waze.com/dashboard My Dashboard section on the Waze website] * '''Read''' the [[global:FAQ|answers to Frequently Asked Questions (FAQ)]] and the [[global:Glossary|glossary]] of terms * '''Participate''' in the [https://www.waze.com/forum/ announcements and discussion forums] '''If you have problems''', try and find your own solution or ask the community for help: * Use the Wiki - there is a search box just to the left * Use the [https://www.waze.com/forum/ Discussion Forums] '''If all else fails''', you can [https://support.google.com/waze/answer/6276841 email Waze with your problem] 07665fcacbec05868a0b96bf0d68581979e10c86 0 6 10446 10429 2017-06-21T08:43:15Z Adabadada 39 /* Philippine Waze Area Manager */ Cleaned up the AM table wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager <u>iPhone expert</u> * deadlockprocess * shogsbro <u>Android expert</u> * zy_pher * Guardian4ngel * shogsbro <u>WME Editing expert</u> * zy_pher * Guardian4ngel * deadlockprocess * shogsbro <u>WME Beta Editor expert</u> * kazmuth * Baldugaras <u>Navigation / Routing expert</u> * deadlockprocess * shogsbro <u>Social Media expert</u> * zy_pher * Guardian4ngel * Adabadada <u>Localization expert</u> * kazmuth <u>Local Champs</u> * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie <u>Wiki Masters</u> * rccoros * kazmuth * Adabadada == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. '''* - Country Manager permissions''' {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Manager/Global Champ |6 |- |SpeedDzel |Philippines |Country Manager/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |rider111 |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |5 |- |deadlockprocess |Philippines |Local Champ |5 |- |Adabadada |Philippines |Local Champ |5 |- |iceden |Philippines |Local Champ |4 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Southern Luzon |Local Champ |4 |- |Ungas |Region IV-A, V |Local Champ |4 |- | SEELE_01 | NCR |Area Manager |3 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR |Area Manager |3 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Cavite |Area Manager |3 |- |Mondskiez |NCR/Zamboanga |Area Manager |3 |- |jojob333 |NCR |Area Manager |3 |- |kabutengkamote |Cavite/Qatar |Area Manager |3 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] 36b1602931ae4a4cb6d009a056c9ea450bf99095 10447 10446 2017-06-21T08:43:48Z Adabadada 39 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager <u>iPhone expert</u> * deadlockprocess * shogsbro <u>Android expert</u> * zy_pher * Guardian4ngel * shogsbro <u>WME Editing expert</u> * zy_pher * Guardian4ngel * deadlockprocess * shogsbro <u>WME Beta Editor expert</u> * kazmuth * Baldugaras <u>Navigation / Routing expert</u> * deadlockprocess * shogsbro <u>Social Media expert</u> * zy_pher * Guardian4ngel * Adabadada <u>Localization expert</u> * kazmuth <u>Local Champs</u> * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie <u>Wiki Masters</u> * rccoros * kazmuth * Adabadada == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Manager/Global Champ |6 |- |SpeedDzel |Philippines |Country Manager/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |rider111 |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |5 |- |deadlockprocess |Philippines |Local Champ |5 |- |Adabadada |Philippines |Local Champ |5 |- |iceden |Philippines |Local Champ |4 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Southern Luzon |Local Champ |4 |- |Ungas |Region IV-A, V |Local Champ |4 |- | SEELE_01 | NCR |Area Manager |3 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR |Area Manager |3 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Cavite |Area Manager |3 |- |Mondskiez |NCR/Zamboanga |Area Manager |3 |- |jojob333 |NCR |Area Manager |3 |- |kabutengkamote |Cavite/Qatar |Area Manager |3 |} '''Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.''' [[Category:Philippines]] f423e78e76562f4626c4c1d8b920c519d28cc40b 10477 10447 2017-08-04T18:16:17Z Adabadada 39 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras * rider111 * zy_pher - Luzon Division Manager * Lu_Wei_Jie - Visayas Division Manager * deadlockprocess - Mindanao Division Manager <u>iPhone expert</u> * deadlockprocess * shogsbro <u>Android expert</u> * zy_pher * Guardian4ngel * shogsbro <u>WME Editing expert</u> * zy_pher * Guardian4ngel * deadlockprocess * shogsbro <u>WME Beta Editor expert</u> * kazmuth * Baldugaras <u>Navigation / Routing expert</u> * deadlockprocess * shogsbro <u>Social Media expert</u> * zy_pher * Guardian4ngel * Adabadada <u>Localization expert</u> * Adabadada * kazmuth <u>Local Champs</u> * iceden * Ungas * zy_pher * Guardian4ngel * deadlockprocess * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie <u>Wiki Masters</u> * rccoros * kazmuth * Adabadada == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Manager/Global Champ |6 |- |SpeedDzel |Philippines |Country Manager/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |rider111 |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |5 |- |deadlockprocess |Philippines |Local Champ |5 |- |Adabadada |Philippines |Local Champ |5 |- |iceden |Philippines |Local Champ |4 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Southern Luzon |Local Champ |4 |- |Ungas |Region IV-A, V |Local Champ |4 |- | SEELE_01 | NCR |Area Manager |3 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR |Area Manager |3 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Cavite |Area Manager |3 |- |Mondskiez |NCR/Zamboanga |Area Manager |3 |- |jojob333 |NCR |Area Manager |3 |- |kabutengkamote |Cavite/Qatar |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 90b23ef27f96c921b148f72e450eb407d6e9ad6b 10479 10477 2017-08-11T11:09:35Z Adabadada 39 /* Philippine Waze Champs and Experts */Cleaned up the list of experts, updated Local Champs roster wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie <u>Wiki Masters</u> * kazmuth * Adabadada <u>Filipino Language Coordinator</u> * Adabadada * kazmuth == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Manager/Global Champ |6 |- |SpeedDzel |Philippines |Country Manager/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |rider111 |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |5 |- |deadlockprocess |Philippines |Local Champ |5 |- |Adabadada |Philippines |Local Champ |5 |- |iceden |Philippines |Local Champ |4 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Southern Luzon |Local Champ |4 |- |Ungas |Region IV-A, V |Local Champ |4 |- | SEELE_01 | NCR |Area Manager |3 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR |Area Manager |3 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Cavite |Area Manager |3 |- |Mondskiez |NCR/Zamboanga |Area Manager |3 |- |jojob333 |NCR |Area Manager |3 |- |kabutengkamote |Cavite/Qatar |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] e41b33c9521178003b62c7e7acb2ea944be737be 10480 10479 2017-08-14T14:21:46Z Adabadada 39 /* Philippine Waze Area Manager */ updated roster of Area Managers wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie <u>Wiki Masters</u> * kazmuth * Adabadada <u>Filipino Language Coordinator</u> * Adabadada * kazmuth == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Manager/Global Champ |6 |- |SpeedDzel |Philippines |Country Manager/Global Champ |6 |- |Baldugaras |Philippines |Country Manager |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |5 |- |Adabadada |Philippines |Local Champ |5 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Southern Luzon |Local Champ |4 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR |Area Manager |3 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Cavite |Area Manager |3 |- |Mondskiez |NCR/Zamboanga |Area Manager |3 |- |jojob333 |NCR |Area Manager |3 |- |kabutengkamote |Cavite/Qatar |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 71b5d9c5c30ded2cc308642ddb96c566165963e1 0 17 10456 2017-06-22T06:16:54Z Adabadada 39 Created Page: Meetups wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: First Waze Local Meetup: June 14, 2014 Venue: F1 Hotel, BGC Malaysia Meetup Indonesia Meetup Global Meetup Baguio Roadtrip: October 18-19, 2014 Venue: The Arc 2015 First Quarter Meetup: Jan. 19, 2015 Venue: Gram's Diner, BGC 5fa49b7b63802182fd13b7d0767cf30cd0a61ee5 10457 10456 2017-06-22T06:17:54Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: First Waze Local Meetup: June 14, 2014 Venue: F1 Hotel, BGC Baguio Roadtrip: October 18-19, 2014 Venue: The Arc 2015 First Quarter Meetup: Jan. 19, 2015 Venue: Gram's Diner, BGC 4a5435ee8a76aee3c0f48442924f6476397fa1d2 10458 10457 2017-06-22T06:40:25Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == June 14, 2014: First Local Meetup Venue: F1 Hotel, BGC October 18-19, 2014: Baguio Roadtrip Venue: The Arc == 2015 == Jan. 19, 2015: 2015 First Quarter Meetup for all Wazers Venue: Gram's Diner, BGC Jan. 27, 2015: Dinner at San Antonio Plaza Feb. 6, 2105: Dinner and Drinks at Burger and Brewskies March 13, 2015: Dinner at Yakimix, Drinks at Chihuahua March 28, 2015: Meetup at Chihuahua June 12, 2015: First Go-kart Meetup Venue: CityKart Makati July 2015: Meetings at with Urban Land Institute Sept. 4, 2015: Dinner at Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup Dec. 4-6, 2015: First SEA Regional Meetup Venue: The Mandarin, Singapore Dec. 30, 2015: Post-Christmas Meetup Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC Venue: 'Cue BGC, Jamba Juice July 10, 2016: Dinner at Puccini Dec. 9, 2016: Pre-regional Meetup Dec. 2016: Second SEA Regional Meetup Venue: Makati Shangri-la, Philippines == 2017 == March 24, 2017: First Meetup 2017 Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Second Meetup at Ooma then drinks at Craft April 15, 2017: Holy Week at Ayala at the 30th 61b52b8d7b321347a45960a6064ef05459052c3a 10459 10458 2017-06-22T06:52:19Z Adabadada 39 /* 2014 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == June 14, 2014: First Local Meetup Venue: F1 Hotel, BGC October 18-19, 2014: Baguio Roadtrip Venue: The Arc Dec. 4, 2014: First Cebu Meetup Venu: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: 2015 First Quarter Meetup for all Wazers Venue: Gram's Diner, BGC Jan. 27, 2015: Dinner at San Antonio Plaza Feb. 6, 2105: Dinner and Drinks at Burger and Brewskies March 13, 2015: Dinner at Yakimix, Drinks at Chihuahua March 28, 2015: Meetup at Chihuahua June 12, 2015: First Go-kart Meetup Venue: CityKart Makati July 2015: Meetings at with Urban Land Institute Sept. 4, 2015: Dinner at Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup Dec. 4-6, 2015: First SEA Regional Meetup Venue: The Mandarin, Singapore Dec. 30, 2015: Post-Christmas Meetup Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC Venue: 'Cue BGC, Jamba Juice July 10, 2016: Dinner at Puccini July 31, 2016: Meetup for all Wazers Venue: Puccini Dec. 9, 2016: Pre-regional Meetup Dec. 2016: Second SEA Regional Meetup Venue: Makati Shangri-la, Philippines == 2017 == Feb. 5, 2017: Meetup for all Wazers Venue: Puccini March 24, 2017: First Meetup 2017 Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Second Meetup at Ooma then drinks at Craft April 15, 2017: Holy Week at Ayala at the 30th 1c3ed477725bf22b4be83e7f400555fac1d1977d 10460 10459 2017-06-22T06:57:21Z Adabadada 39 /* 2016 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == June 14, 2014: First Local Meetup Venue: F1 Hotel, BGC October 18-19, 2014: Baguio Roadtrip Venue: The Arc Dec. 4, 2014: First Cebu Meetup Venu: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: 2015 First Quarter Meetup for all Wazers Venue: Gram's Diner, BGC Jan. 27, 2015: Dinner at San Antonio Plaza Feb. 6, 2105: Dinner and Drinks at Burger and Brewskies March 13, 2015: Dinner at Yakimix, Drinks at Chihuahua March 28, 2015: Meetup at Chihuahua June 12, 2015: First Go-kart Meetup Venue: CityKart Makati July 2015: Meetings at with Urban Land Institute Sept. 4, 2015: Dinner at Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup Dec. 4-6, 2015: First SEA Regional Meetup Venue: The Mandarin, Singapore Dec. 30, 2015: Post-Christmas Meetup Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC Venue: 'Cue BGC, Jamba Juice July 10, 2016: Dinner at Puccini July 31, 2016: Meetup for all Wazers Venue: Puccini Dec. 8, 2016: Pre-regional Meetup Dec. 9-1, 2016: Second SEA Regional Meetup Venue: Makati Shangri-la, Philippines == 2017 == Feb. 5, 2017: Meetup for all Wazers Venue: Puccini March 24, 2017: First Meetup 2017 Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Second Meetup at Ooma then drinks at Craft April 15, 2017: Holy Week at Ayala at the 30th e824669787c7a16b8ecc735247cda773832d897f 10461 10460 2017-06-22T06:58:36Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: 2015 First Quarter Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Dinner <br /> San Antonio Plaza Feb. 6, 2105: Dinner and Drinks <br /> Burger and Brewskies March 13, 2015: Dinner at Yakimix, Drinks at Chihuahua March 28, 2015: Meetup at Chihuahua June 12, 2015: First Go-kart Meetup Venue: CityKart Makati July 2015: Meetings at with Urban Land Institute Sept. 4, 2015: Dinner at Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup Dec. 4-6, 2015: First SEA Regional Meetup Venue: The Mandarin, Singapore Dec. 30, 2015: Post-Christmas Meetup Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC Venue: 'Cue BGC, Jamba Juice July 10, 2016: Dinner at Puccini July 31, 2016: Meetup for all Wazers Venue: Puccini Dec. 8, 2016: Pre-regional Meetup Dec. 9-1, 2016: Second SEA Regional Meetup Venue: Makati Shangri-la, Philippines == 2017 == Feb. 5, 2017: Meetup for all Wazers Venue: Puccini March 24, 2017: First Meetup 2017 Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Second Meetup at Ooma then drinks at Craft April 15, 2017: Holy Week at Ayala at the 30th 81a4292e6f59e639f9de8c70a28e3ce156658f0e 10462 10461 2017-06-22T06:59:51Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: 2015 First Quarter Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Dinner <br /> San Antonio Plaza Feb. 6, 2105: Dinner and Drinks <br /> Burger and Brewskies March 13, 2015: Dinner at Yakimix, Drinks at <br /> Chihuahua March 28, 2015: Meetup at <br /> Chihuahua June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings at with Urban Land Institute Sept. 4, 2015: Dinner at <br /> Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup Venue: CityKart Makati Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: The Mandarin, Singapore Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC Venue: 'Cue BGC, Jamba Juice July 10, 2016: Dinner at Puccini July 31, 2016: Meetup for all Wazers Venue: Puccini Dec. 8, 2016: Pre-regional Meetup Dec. 9-1, 2016: Second SEA Regional Meetup Venue: Makati Shangri-la, Philippines == 2017 == Feb. 5, 2017: Meetup for all Wazers Venue: Puccini March 24, 2017: First Meetup 2017 Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Second Meetup at Ooma then drinks at Craft April 15, 2017: Holy Week at Ayala at the 30th 580236a070281ad75a46babd8cce7899ad827128 10463 10462 2017-06-22T07:01:26Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: 2015 First Quarter Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Dinner <br /> San Antonio Plaza Feb. 6, 2105: Dinner and Drinks <br /> Burger and Brewskies March 13, 2015: Dinner at Yakimix, Drinks at <br /> Chihuahua March 28, 2015: Meetup at <br /> Chihuahua June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings at with Urban Land Institute Sept. 4, 2015: Dinner at <br /> Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup Venue: CityKart Makati Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: The Mandarin, Singapore Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BGC, Jamba Juice July 10, 2016: Dinner <br /> Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Pre-regional Meetup Venue: Draft, Farmacy Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines == 2017 == Feb. 5, 2017: Meetup for all Wazers Venue: Puccini March 24, 2017: First Meetup 2017 Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Second Meetup at Ooma then drinks at Craft April 15, 2017: Holy Week at Ayala at the 30th a3b32a183fb4667d52e2d5844beddfee4a81a599 10464 10463 2017-06-22T07:02:32Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: 2015 First Quarter Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Dinner <br /> San Antonio Plaza Feb. 6, 2105: Dinner and Drinks <br /> Burger and Brewskies March 13, 2015: Dinner at Yakimix, Drinks at <br /> Chihuahua March 28, 2015: Meetup at <br /> Chihuahua June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings at with Urban Land Institute Sept. 4, 2015: Dinner at <br /> Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup Venue: CityKart Makati Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: The Mandarin, Singapore Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BGC, Jamba Juice July 10, 2016: Dinner <br /> Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Pre-regional Meetup Venue: Draft, Farmacy Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: First Meetup 2017 <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Second Meetup at <br /> Ooma then drinks at Craft April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi b362c416ac1b5cfc0e98045a680ad403410cfeaf 10465 10464 2017-06-22T07:13:36Z Adabadada 39 /* 2015 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup Venue: CityKart Makati Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi cd9d160be6b08ee9631cca82de6287bb97b4c6ee 10466 10465 2017-06-22T07:14:33Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi c715cb974884512cd4cc259e4894115e88455fdf 10467 10466 2017-06-22T07:16:12Z Adabadada 39 /* 2014 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == '''June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi 1878a18cdf086d35b78d98686cef6cf73fb777d8 10468 10467 2017-06-22T07:41:04Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == '''June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines''' [[File:IMG 20161213 172547.jpg|frameless|right|Filipino delegates to the 2nd SEA Regional Meetup]] == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi cbe25e2718e16272aded1d31f33396388ad86691 10469 10468 2017-06-22T07:45:18Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == '''June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi 1878a18cdf086d35b78d98686cef6cf73fb777d8 10470 10469 2017-06-22T15:36:41Z Adabadada 39 /* 2016 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == '''June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS May 14, 2016: Waze Cafe - MapRaid Awards Venue: Mona Lisa Ristorante, SM Aura July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi 6a4274cc2e97a174399b139b4a1ebe6ac1a0cfa0 10471 10470 2017-06-22T15:37:05Z Adabadada 39 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == '''June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS May 14, 2016: Waze Cafe - MapRaid Awards <br /> Venue: Mona Lisa Ristorante, SM Aura July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi 7631bf2d9e8d58060d2adbc86d59aa71136f8c90 10472 10471 2017-06-22T15:37:43Z Adabadada 39 /* 2016 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == '''June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br /> Venue: Mona Lisa Ristorante, SM Aura''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-1, 2016: Second SEA Regional Meetup <br /> Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi 30c2faf63c49c187b56208f2a2c06bb05073cb2f 0 2 10473 10430 2017-07-10T02:25:19Z Kazmuth 35 /* General Guidelines on Road Editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable. * There are a lot of roads intersecting which can only turn onto the nearest direction of travel. * Google Maps or other mapping source show it as a split road * The non-drivable median is interrupted by a cross segment at most intersections. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. [[Category:Philippines]] 413b742d1a020e680e86b8687f940e3e61fce5a3 0 14 10476 10423 2017-07-18T23:57:43Z Kazmuth 35 /* I've been blocked and I can't edit on WME or send a report through the app */ wikitext text/x-wiki __TOC__ *'''Here are the most asked questions from Pinoy Waze Editors''' ==Is there a manual for Waze map editing?== There is a [[global:Waze_Map_Editor|Waze Map Editor]] manual that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [[Philippines/Editing resources |Editing Resources for the Philippines]] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed on our guide are specifically for our pinoy roads and driving habits. ==I've been blocked and I can't edit on WME or send a report through the app== If you have received a message on the app or an email notification that you have been blocked, this is because of either 1. You have been detected by the Waze system as massively reporting. or 2. You have been reported by the community because you are violating the rules imposed by Waze and/or the community. If #1 is the case, even if we could, we will not help you with this. Like Waze, we do not tolerate cheating, and will not lift a finger to help you get unblocked or unbanned. By spamming the reports function you intentionally send out wrong, inconsistent, spurious, or unneeded data. You are also skewing the data being collected by Waze making the aggregate data inaccurate. If you fall under #2 then what you should do is 1. Read the wiki, particularly the [[Philippines]] section so you can figure out what you did wrong 2. Join the [https://www.facebook.com/groups/WazePhilippines/ Waze Philippines FB Group] 3. Join the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg Waze Philippines Telegram channel] 4. Post a message on the FB group or the Telegram channel and tell us your predicament. If you fail to read the wiki and figure out why you were blocked, we will not help you. ==Why am I not leveling up to Level 2 or 3?== We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]), have joined at least 1 [[Philippines/MapRaid_History|PH MapRaid]], have attended the "Intro to Map Editing Webinar", and have joined the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg PH Telegram channel]. This means all Waze editors will be force-ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. ''New Area Managers are also not automatically promoted to Level 3 and will remain at their level until the local champs agree to promote based on the quality of edits''. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] ==How do I apply to be an Area Manager?== To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[global:Area_Manager|Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] ==How long does it take until my edits gets displayed on my Waze app?== It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area ==When I encounter traffic on the road, what type do I report?== You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph ==I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?== The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are '''NO ROADS''' which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, and most Expressways. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps because of report abuse. You will still be able to report them but they will no longer appear on WME and you will not get any points for them. ==What is the difference between Map Problems and Update Requests?== Map Problems or MPs are Waze generated and based on analyzed Wazer traffic. Update Requests or URs are Waze user submitted requests to fix user identified map issues. ==How do I fix Map Problems?== Visit the [[global:Map_Problems_in_Waze_Map_Editor|Map Problem]] wiki for more details. ==How do I fix Update Requests?== Visit the [[global:Update_Requests_in_Waze_Map_Editor|Update Requests]] wiki for more details. ==Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?== On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. ==Waze does not use the U-Turn segment I created between two roads, what could be the problem?== Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. ==Are there any shortcut keys for the Waze Map Editor?== You can view the wiki page on [[global:Keyboard_shortcuts|Keyboard shortcuts]] ==Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?== Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. ==I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?== You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. ==The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?== The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. ==There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?== You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the Partial[[global:Partial_restrictions| restrictions]] wiki. ==Search function doesn't work, how do I fix it?== This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. ==I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?== If refreshing the map editor does not work, go to [http://status.waze.com the Waze status page] and check for any announcement from Waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==How do I report flooding so that Wazers will not be routed on a flooded road?== Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report an unpassable road due to flooding, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank, and the country. *The road will be opened when Waze detects that a number of users have driven through the road. [[Category:Philippines]] c64bb6beb11b0e24f079806ea5f13a8d15f2fed3 0 2 10481 10473 2017-09-01T14:14:45Z Adabadada 39 /* General Guidelines on Road Editing */ Edited criteria for splitting/unsplitting wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. [[Category:Philippines]] b65aeb504aa51ad6bd6e61124523bb28188fb016 10488 10481 2017-09-17T03:25:36Z Kazmuth 35 wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] 85965d5dfbfa6b66976cbaad4761dff366954ec8 10501 10488 2017-10-16T06:04:07Z Kazmuth 35 /* General Guidelines on Road Editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] ec438b699e1cca1984bc11f08bf35b90bc3cb339 10503 10501 2017-12-30T07:48:40Z Kazmuth 35 wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain the areas they manage. This means, L3+ editors SHOULD first work on their immediate vicinity. The reason for this is because they should have first hand information and are familiar with their areas. They don't need to send messages to reporters to ask questions and this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc # Repeat step 3 and 4 By doing this, you should be able to create a clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs in the Philippines # Place Update Requests - Do this next if you have cleared ALL the URs # System Detected Problems - Also known as Map Problems '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be points whore # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation if even part of the place is in the perimeter. You are just doing this for points # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] 2000997786a227505bbff142e89a1de648158fd7 10504 10503 2017-12-30T07:55:34Z Kazmuth 35 /* Map Editing Priorities */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain the areas they manage. This means, L3+ editors SHOULD first work on their immediate vicinity. The reason for this is because you should have first hand information and are familiar with your areas. You don't need to send messages to reporters to ask questions and this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc # Repeat step 3 and 4 By doing this, you should be able to create a clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs we have. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as it may be valid issues. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation if even part of the place is in the perimeter. You are just doing this for points # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] fc36a9975b93db5b88dcdd58399477b0ce374d5c 10505 10504 2017-12-30T08:08:41Z Kazmuth 35 /* Map Editing Priorities */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain the area where they live. This means, L3+ editors SHOULD first work on their immediate vicinity. The reason for this is because you should have first hand information and are familiar with your areas. You don't need to send messages to reporters to ask questions and this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc # Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs we have. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as it may be valid issues. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is in the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] 57fb2f01b8a11712089947fa93f510cde788ed45 10506 10505 2018-01-06T10:47:19Z Kazmuth 35 /* Map Editing Priorities */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain and update the area where they live. This means, L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc. # Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues. # Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] cd89def0f8b5abd82ff4f08a2acfcf78524a60b1 10507 10506 2018-01-06T10:59:56Z Kazmuth 35 /* Real Time Closures */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain and update the area where they live. This means, L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc. # Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues. # Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. If you need to set an RTC that is more than a month long, make sure you check on it at least once a week. There have been a lot of instances where RTCs for several months have been placed and then never checked again. This resulted in segments being closed off from routing long after they have reopened. URs were piling up on the area due to this and routing has been severely affected on the area. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === This feature has been disabled for the country. Do not try to add speed cameras to the map. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] d5eb9e2662a2be47574433752bec64abf1a40a15 10508 10507 2018-01-06T11:01:47Z Kazmuth 35 /* Speed Cameras */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain and update the area where they live. This means, L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc. # Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues. # Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. === General Guidelines on Road Editing === 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. === General Guidelines on Editing Places === Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. If you need to set an RTC that is more than a month long, make sure you check on it at least once a week. There have been a lot of instances where RTCs for several months have been placed and then never checked again. This resulted in segments being closed off from routing long after they have reopened. URs were piling up on the area due to this and routing has been severely affected on the area. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === Adding any form of camera from the app has been disabled. This can only be added on WME by high level editors. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] f17e8c89710496e47139c6d143c12b502ebb372c 10509 10508 2018-01-06T11:05:13Z Kazmuth 35 wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain and update the area where they live. This means, L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc. # Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues. # Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. == General Guidelines on Road Editing == 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit' # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == General Guidelines on Editing Places == Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination == General Guidelines on other WME Objects == === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. If you need to set an RTC that is more than a month long, make sure you check on it at least once a week. There have been a lot of instances where RTCs for several months have been placed and then never checked again. This resulted in segments being closed off from routing long after they have reopened. URs were piling up on the area due to this and routing has been severely affected on the area. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === Adding any form of camera from the app has been disabled. This can only be added on WME by high level editors. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] 331688183a73546d264e3c6370a3412c51363a8b 10510 10509 2018-04-17T10:02:05Z Kazmuth 35 /* General Guidelines on Road Editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain and update the area where they live. This means, L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc. # Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues. # Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. == General Guidelines on Road Editing == 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" except if it will immediately fork into two exits # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit'. Segment names are not localized so it will sound awkward when the rest of the instructions are in Filipino. # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == General Guidelines on Editing Places == Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination == General Guidelines on other WME Objects == === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. If you need to set an RTC that is more than a month long, make sure you check on it at least once a week. There have been a lot of instances where RTCs for several months have been placed and then never checked again. This resulted in segments being closed off from routing long after they have reopened. URs were piling up on the area due to this and routing has been severely affected on the area. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === Adding any form of camera from the app has been disabled. This can only be added on WME by high level editors. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] 0cf555fca0980a497b6cf83882f14a5470da6f91 10511 10510 2018-04-17T10:10:32Z Kazmuth 35 /* General Guidelines on Road Editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain and update the area where they live. This means, L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc. # Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues. # Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. == General Guidelines on Road Editing == 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" except if it will immediately fork into two exits. Or the exit leads to two separate turns # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit'. Segment names are not localized so it will sound awkward when the rest of the instructions are in Filipino. # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == General Guidelines on Editing Places == Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination == General Guidelines on other WME Objects == === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. If you need to set an RTC that is more than a month long, make sure you check on it at least once a week. There have been a lot of instances where RTCs for several months have been placed and then never checked again. This resulted in segments being closed off from routing long after they have reopened. URs were piling up on the area due to this and routing has been severely affected on the area. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === Adding any form of camera from the app has been disabled. This can only be added on WME by high level editors. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] 96c9f8eb16a80634b3a844f5cc3df7755aebe1d7 0 17 10482 10472 2017-09-02T07:03:37Z Rccoros 5 /* 2016 */ Fix typo on date of SEA Regional Meetup /* 2017 */ Added 2nd National Meetup wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2014 == '''June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br /> Venue: Mona Lisa Ristorante, SM Aura''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines b9df6a6241a445854adf9155aa74460da205efcc 10493 10482 2017-09-28T00:31:45Z Kazmuth 35 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == June 8, 2013: First Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC June 14, 2014: First Local Meetup <br /> Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br /> Venue: Mona Lisa Ristorante, SM Aura''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines dbed267e55be7348e3ca07aabcffa30ddcb7d652 10494 10493 2017-09-28T00:40:02Z Kazmuth 35 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 4, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi ''''''July 1, 2017: SEA Regional Beta Meetup '''<br />''' Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines 70347b1540dda8d5a7a396e148df07192e0e0b61 10495 10494 2017-09-28T00:49:02Z Kazmuth 35 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 4, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi ''''July 1, 2017: SEA Regional Beta Meetup '''<br />' Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines 45b29f26e550d2a4b34dd7f8db25e9438f1f9c23 10496 10495 2017-09-28T00:57:53Z Kazmuth 35 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 4, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi ''''July 1, 2017: SEA Regional Beta Meetup '''<br />' Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines 4b313a318e5692f861f389d414d71f5fdf94071b 10497 10496 2017-09-28T00:59:30Z Kazmuth 35 /* 2017 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 4, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''July 1, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines cc50ddee42d6f3ff35b3ec3df6d0e2fd560623ae 10498 10497 2017-09-28T01:01:35Z Kazmuth 35 /* 2017 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 3-5, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''June 30 - July 2, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines 1ad7af08e5a10bd83d15542d01ff39bd55ad7a95 10514 10498 2018-07-11T12:12:14Z Rccoros 5 added 2017 Regional Meetup and the Mega Meetup last April 2018 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 3-5, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''June 30 - July 2, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines '''December 1 - 2, 2017: Waze APAC Regional Meetup 2017 '''<br /> Venue: Pullman Bangkok King Power, Thailand == 2018 == '''April 13 - 15, 2018: Waze APAC Mega Regional Meetup <br />''' Venue: ParkRoyal on Pickering, Singapore 76049ab73918cf0f683a3334e1dadc84cfda7e85 10515 10514 2018-07-11T12:15:22Z Rccoros 5 /* 2018 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 3-5, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''June 30 - July 2, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines '''December 1 - 2, 2017: Waze APAC Regional Meetup 2017 '''<br /> Venue: Pullman Bangkok King Power, Thailand == 2018 == '''April 13 - 15, 2018: Waze APAC Mega Regional Meetup <br />''' Venue: ParkRoyal on Pickering, Singapore '''May 27, 2018: Southies Meetup <br />''' Venue: Bawai’s Vietnamese Kitchen, Nuvali 56aeb1d0945febbe3209eca8b2d4b7625f7d281f 10516 10515 2018-07-11T12:15:35Z Rccoros 5 /* 2018 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 3-5, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''June 30 - July 2, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines '''December 1 - 2, 2017: Waze APAC Regional Meetup 2017 '''<br /> Venue: Pullman Bangkok King Power, Thailand == 2018 == '''April 13 - 15, 2018: Waze APAC Mega Regional Meetup <br />''' Venue: ParkRoyal on Pickering, Singapore May 27, 2018: Southies Meetup <br /> Venue: Bawai’s Vietnamese Kitchen, Nuvali cd41070fb1fce0397a27a3d3508b93d0c01dcafd 10521 10516 2019-04-29T08:30:39Z Rccoros 5 Added meetups for 2018 and 2019 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 3-5, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''June 30 - July 2, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines '''December 1 - 2, 2017: Waze APAC Regional Meetup 2017 '''<br /> Venue: Pullman Bangkok King Power, Thailand == 2018 == '''April 13 - 15, 2018: Waze APAC Mega Regional Meetup <br />''' Venue: ParkRoyal on Pickering, Singapore May 27, 2018: Southies Meetup <br /> Venue: Bawai’s Vietnamese Kitchen, Nuvali '''Aug. 18, 2018: Third National Meetup <br />''' Venue: Crowne Plaza Manila, Philippines '''October 12 - 14, 2018: BetaLization Meetup <br />''' Venue: Courtyard by Marriott Berlin City Center, Germany == 2019 == '''April 12 - 14, 2019: Waze APAC Mega Regional Meetup <br />''' Venue: Pullman Bangkok King Power, Thailand 7523c35941d6f1c8d780852e2040a71653f146e8 10522 10521 2019-04-29T08:40:51Z Rccoros 5 Added Recent Waze Cafe and Holy Week meet wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 3-5, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''June 30 - July 2, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines '''December 1 - 2, 2017: Waze APAC Regional Meetup 2017 '''<br /> Venue: Pullman Bangkok King Power, Thailand == 2018 == '''April 13 - 15, 2018: Waze APAC Mega Regional Meetup <br />''' Venue: ParkRoyal on Pickering, Singapore May 27, 2018: Southies Meetup <br /> Venue: Bawai’s Vietnamese Kitchen, Nuvali '''Aug. 18, 2018: Third National Meetup <br />''' Venue: Crowne Plaza Manila, Philippines '''October 12 - 14, 2018: BetaLization Meetup <br />''' Venue: Courtyard by Marriott Berlin City Center, Germany == 2019 == February 3, 2019: Waze Cafe Venue: UP Diliman '''April 12 - 14, 2019: Waze APAC Mega Regional Meetup <br />''' Venue: Pullman Bangkok King Power, Thailand April 19, 2019: Holy Week at BGC <br /> Venue: Pink's Hot Dogs 8a055e6e6dbebe32ecd7165bac5f009261862fc9 0 1 10483 10478 2017-09-07T05:53:21Z Shogsbro 40 Added steps for new editor to join the community wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == New editors wishing to edit in Philiipines, please: # Fill out [[this questionnaire]] to provide us with a profile of your experience and how to contact you # Install [[Telegram]] (or use the [[Web version]]), create a username, join the [[public group]], and announce yourself :-) # If you use Facebook, like [https://www.facebook.com/WazePhilippines/ our page] (where we share announcements) and join [[our group]] (for discussion) (This section under construction for the PH. Links to other Local Pages for now) * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3Q_LenyNej5Fg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 23897a1ab4b75f3dff90b852017acd5378f11c07 10484 10483 2017-09-07T05:54:49Z Shogsbro 40 Fix up language wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == New editors wishing to edit in Philiipines, please: # Fill out [[this questionnaire]] to provide us with a profile of your experience and how to contact you # Install [[Telegram]] (or use the [[Web version]]), create a username, join the [[public group]], and announce yourself :-) # If you use Facebook, like [https://www.facebook.com/WazePhilippines/ our page] (where we share announcements) and join [[our group]] (for discussion) We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3Q_LenyNej5Fg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 8920b64d49c7a0c078f2c8b8aa39a4b1172b6d09 10485 10484 2017-09-15T05:17:01Z Kazmuth 35 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg Philippines Local Meetup 2017 </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == New editors wishing to edit in Philiipines, please: # Fill out [[this questionnaire]] to provide us with a profile of your experience and how to contact you # Install [[Telegram]] (or use the [[Web version]]), create a username, join the [[public group]], and announce yourself :-) # If you use Facebook, like [https://www.facebook.com/WazePhilippines/ our page] (where we share announcements) and join [[our group]] (for discussion) We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3Q_LenyNej5Fg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 039766d73d0f309e8d0f6e47bf332e6115b01297 10486 10485 2017-09-15T05:21:20Z Kazmuth 35 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps. ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == New editors wishing to edit in Philiipines, please: # Fill out [[this questionnaire]] to provide us with a profile of your experience and how to contact you # Install [[Telegram]] (or use the [[Web version]]), create a username, join the [[public group]], and announce yourself :-) # If you use Facebook, like [https://www.facebook.com/WazePhilippines/ our page] (where we share announcements) and join [[our group]] (for discussion) We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3Q_LenyNej5Fg Philippine Wazers' Telegram chat group] [[Category:Philippines]] 9dc3e8b2d8c9d70a1c3a27e294e1ff1f0ce2c6d6 10487 10486 2017-09-15T05:21:47Z Kazmuth 35 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == New editors wishing to edit in Philiipines, please: # Fill out [[this questionnaire]] to provide us with a profile of your experience and how to contact you # Install [[Telegram]] (or use the [[Web version]]), create a username, join the [[public group]], and announce yourself :-) # If you use Facebook, like [https://www.facebook.com/WazePhilippines/ our page] (where we share announcements) and join [[our group]] (for discussion) We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Categories * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3Q_LenyNej5Fg Philippine Wazers' Telegram chat group] [[Category:Philippines]] ed0e46808676c93688e97918250572d7a49169c1 10490 10487 2017-09-27T15:16:33Z Adabadada 39 /* Editing Guidelines for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == New to Editing? Start Here == New editors wishing to edit in Philiipines, please: # Fill out [[this questionnaire]] to provide us with a profile of your experience and how to contact you # Install [[Telegram]] (or use the [[Web version]]), create a username, join the [[public group]], and announce yourself :-) # If you use Facebook, like [https://www.facebook.com/WazePhilippines/ our page] (where we share announcements) and join [[our group]] (for discussion) We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Harmonization Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) == Philippine Waze Community== The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3Q_LenyNej5Fg Philippine Wazers' Telegram chat group] [[Category:Philippines]] ba41f72e24b6cca285a4e8f7373ae7c573a354a3 10500 10490 2017-09-28T10:14:24Z Adabadada 39 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3Q_LenyNej5Fg Philippine Wazers' Telegram chat group] == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * Place Harmonization Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] e896cbc1171b1f43a99684e15c2d84f827ee8378 10502 10500 2017-12-06T06:02:18Z Kazmuth 35 /* Editing Guidelines for the Philippines */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3Q_LenyNej5Fg Philippine Wazers' Telegram chat group] == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/spreadsheets/d/19aW9soivK6czlE45zBEZyp0oUHccoYSdLUm_5lR1Msw/edit?usp=sharing Place Harmonization] Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] 7a342d462891ae8aa065b27e0c67c0aa3154aa4e 10513 10502 2018-06-29T03:18:57Z Kazmuth 35 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3TyzFma6EuoTA Philippine Wazers' Telegram chat group] == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/spreadsheets/d/19aW9soivK6czlE45zBEZyp0oUHccoYSdLUm_5lR1Msw/edit?usp=sharing Place Harmonization] Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] 0828fec26c18139415d00f2fc73ae6f0c1dcb692 10517 10513 2018-07-16T16:06:11Z Rccoros 5 /* External Editing Resources for the Philippines */ Updated Road and Bridge inventory link wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3TyzFma6EuoTA Philippine Wazers' Telegram chat group] == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/spreadsheets/d/19aW9soivK6czlE45zBEZyp0oUHccoYSdLUm_5lR1Msw/edit?usp=sharing Place Harmonization] Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://dpwh.maps.arcgis.com/apps/webappviewer/index.html?id=4bc4f2dc3a5644088c57de02108a8fd3 DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] 3b56ea1cf3bbb331de124d23dbd812ffdb7987e2 10518 10517 2019-02-19T03:18:28Z Kazmuth 35 wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AgCmlz-Od3RXEcpfHnoTLA Philippine Wazers' Telegram chat group] == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/spreadsheets/d/19aW9soivK6czlE45zBEZyp0oUHccoYSdLUm_5lR1Msw/edit?usp=sharing Place Harmonization] Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://dpwh.maps.arcgis.com/apps/webappviewer/index.html?id=4bc4f2dc3a5644088c57de02108a8fd3 DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] 2630ab65bddfb87b8dee593db5595bb6dbaeb262 10523 10518 2019-06-14T15:56:53Z Adabadada 39 Changed link wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * Philippine Wazers' Telegram chat group == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/spreadsheets/d/19aW9soivK6czlE45zBEZyp0oUHccoYSdLUm_5lR1Msw/edit?usp=sharing Place Harmonization] Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://dpwh.maps.arcgis.com/apps/webappviewer/index.html?id=4bc4f2dc3a5644088c57de02108a8fd3 DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] 1632db89d2df9e848f011a1b15cb9c54d476c030 10524 10523 2019-06-14T16:02:56Z Adabadada 39 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [[Tg://join?invite=AuGgzD-Od3SNAztluS9EUA|Philippine Wazers' Telegram chat group]] == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/spreadsheets/d/19aW9soivK6czlE45zBEZyp0oUHccoYSdLUm_5lR1Msw/edit?usp=sharing Place Harmonization] Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://dpwh.maps.arcgis.com/apps/webappviewer/index.html?id=4bc4f2dc3a5644088c57de02108a8fd3 DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] 86c6cbc2eb2b1a333127c6c0db1b0cc35bfb71f9 10525 10524 2019-06-14T16:06:35Z Adabadada 39 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * Philippine Wazers' Telegram chat group == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/spreadsheets/d/19aW9soivK6czlE45zBEZyp0oUHccoYSdLUm_5lR1Msw/edit?usp=sharing Place Harmonization] Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://dpwh.maps.arcgis.com/apps/webappviewer/index.html?id=4bc4f2dc3a5644088c57de02108a8fd3 DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] 1632db89d2df9e848f011a1b15cb9c54d476c030 10526 10525 2019-06-14T16:12:39Z Adabadada 39 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [tg://join?invite=AuGgzD-Od3SNAztluS9EUA Philippine Wazers' Telegram chat group] == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/spreadsheets/d/19aW9soivK6czlE45zBEZyp0oUHccoYSdLUm_5lR1Msw/edit?usp=sharing Place Harmonization] Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://dpwh.maps.arcgis.com/apps/webappviewer/index.html?id=4bc4f2dc3a5644088c57de02108a8fd3 DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] 926eb18678ddad23d294c4a83ab47656f4218dc0 10527 10526 2019-06-14T16:14:36Z Adabadada 39 /* Philippine Waze Community */ wikitext text/x-wiki <big>'''The Complete Guide to Waze in the Philippines'''</big> Welcome, Pinoy Wazer! If you are reading this then you probably want to learn more about how to use Waze or edit the Waze map. This may be because you want to add a new road or have found a map issue and want to contribute to the Waze community. You have come to the right place! Read up on the global standards and guidelines referred to here as well as our own guide for editing the Philippine roads before attempting to edit the maps.<gallery> File:PH Local 2017.jpg </gallery> ==[[About|About Waze]]== {{:Main/About Waze}} ==[[Getting Started]]== {{:Getting Started}} == Philippine Waze Community == The Philippine community of Waze editors is a close-knit group and are constantly in communication. All editors who wish to edit in the Philippines are required to join the community, whether on Facebook, Telegram, or on the forums. Those who refuse to join have no chance to become a trusted editor. The Facebook group is where all Waze users are welcome to share Waze- and traffic-related information. The primary means of communication of the Pinoy editors, however, is Telegram. * Self-management statement * [[Philippines/Champs_And_AMs |Champs and AMs ]] Meet the PH Global and Local Champs and the Area Managers * [[Meetups]] * [[Philippines/MapRaid History |MapRaid History ]] Statistics on MapRaids conducted in the Philippines * [https://www.facebook.com/WazePhilippines/ Waze Philippines Facebook Page] * [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] * [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group] * [https://twitter.com/PhilWazers Philippine Waze Users Twitter] * [https://t.me/joinchat/AuGgzD-Od3SNAztluS9EUA Philippine Wazers' Telegram chat group] == New to Editing? Start Here == We will be updating this section with local specific policies, but whilst it is under construction please review these other links for now: * [[global:Waze_Map_Editor|Waze Map Editor Manual]] * [[usa:Edits_to_avoid|Edits to avoid]] - '''REQUIRED READING FOR ALL EDITORS, ESPECIALLY NEWBIES''' (Note that this is for the USA but most are applicable to Waze Philippines as well) * [[global:Best_map_editing_practice|Best map editing practice]] == Editing Guidelines for the Philippines== * [[Philippines/Editing resources|Editing resources]] Specific guidelines for editing in the Philippines, tailored to our roads and driving habits * Road Editing * [[Philippines/Places_Policy |Places Policy ]] Guidelines for editing places and handling Place Update Requests * [https://docs.google.com/spreadsheets/d/19aW9soivK6czlE45zBEZyp0oUHccoYSdLUm_5lR1Msw/edit?usp=sharing Place Harmonization] Standards for place categories, types, and naming. * [[Philippines/Update_Requests |Update Requests ]] What to do with Update Requests (URs) * [[Philippines/Speedlimit |Speedlimit ]] Speed limits in accordance with ''REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed''. * [[Philippines/Locking |Locking ]] Why are segments and places locked? * [[Philippines/Other Questions and Tips|Other Questions and Tips]] Other Questions and Tips for the Pinoy Waze Editor == External Editing Resources for the Philippines == * [https://docs.google.com/forms/d/14rNFrlsvDkAPHEGFEYQ7rPTdqp_HllnO5mxD7fdYAuY/viewform Waze Philippines Editor Mentoring Program] - If you would like to learn more about editing, you can enter the editing mentoring program where a senior editor will guide you and help you learn how to edit properly. * [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] - If you are confident enough with your editing skills and you have met the requirements listed in the [[Philippines/Champs And AMs|Philippines Area Managers]] section, you can apply to be an Area Manager in the Philippines using this form. We will send you an email regarding the next steps. If we don't hear from you within a week from our email, we will assume that you are no longer pursuing your application. * [http://en.wikipedia.org/wiki/List_of_expressways_in_the_Philippines Philippine Tollways] - Here is a complete list of tollways in the Philippines on Wikipedia. * [http://en.wikipedia.org/wiki/Highways_in_the_Philippines Philippine Highways] - Another list which contains Major Highways, Tollways and expressways, Manila Arterial Road System as well as notable provincial highways and bridges on Wikipedia. * [https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit#gid=0 Philippines TTS List] - A complete list of supported TTS abbreviations and custom name pronunciations * [http://dpwh.maps.arcgis.com/apps/webappviewer/index.html?id=4bc4f2dc3a5644088c57de02108a8fd3 DPWH National Roads and Bridges Inventory] - A list of all roads and bridges in the Philippines with their official names and locations. This also indicates their route number (RNS) [[Category:Philippines]] d12c2d407c811d932828b931db81bc9853bd09bd 0 13 10489 10353 2017-09-27T15:05:18Z Adabadada 39 wikitext text/x-wiki The speedlimits in the Philippines are stated in [http://www.gov.ph/1964/06/20/republic-act-no-4136/ REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed.'' They are as follows: {| class="wikitable sortable" |- ! Maximum allowed speed in KPH !! Cars and Motorcycles !! Trucks and Buses |- | Expressways || 100 || 80 |- | Major Highways || 80 || 60 |- | Minor Highways || 60 || 60 |- | Primary Roads, On/Off Ramps || 40 || 40 |- | Streets, except those with speedbumps (humps) || 30 || 30 |- | Private & Parking Lot roads, Streets with speedbumps (humps) || 20 / Depends on traffic regulations of the area || 20 / Depends on traffic regulations of the area |} '''IMPORTANT NOTE WHEN SETTING SPEEDLIMITS:''' Set the speedlimit according to the road classification in real life, not according to what it was classified as on the WME. [[Category:Philippines]] 4e84286bf7c0bbcb5c88af5357eec5fcac78856d 0 18 10491 2017-09-27T15:26:28Z Adabadada 39 Wrote introduction for PH Harmonization wikitext text/x-wiki The community has come up with several agreements on how to map specific places and editors in the Philippines are expected to adhere to these standards. This is not meant to be comprehensive and it may change over time. It is therefore important to stay in touch with the community so as to keep abreast of these changes. If you are intent on editing places, please keep these tables on hand at all times. 0c808889908b93f6418d9bacac7e5cc79ef695f4 10492 10491 2017-09-27T16:04:46Z Adabadada 39 Added place category table wikitext text/x-wiki The community has come up with several agreements on how to map specific places and editors in the Philippines are expected to adhere to these standards. This is not meant to be comprehensive and it may change over time. It is therefore important to stay in touch with the community so as to keep abreast of these changes. If you are intent on editing places, please keep these tables on hand at all times. {| !'''Place''' !'''Primary Category''' !'''Additional Category''' !'''Type''' !'''Comments''' |- |24 hour mini marts and sari-sari stores |Convenience Store | |Point (may be Area if large enough) |7 Eleven, Ministop, Lawson, Family Mart |- |Barangay Hall |Government |Organization/Association |Point | |- |Beach Resort |Beach | |Point (may be Area if Landmark) |Add category as appropriate: Lodging, Swimming Pool |- |Church/Chapel |Religious Center | |Point (may be Area if large enough) | |- |City Hall |City Hall | |Point (may be Area if large enough) | |- |Clubhouse |Organization/Association; Convention/Event Center | |Point (may be Area if large enough) | |- |Cockpit |Sports Court | |Point (may be Area if large enough) | |- |Commercial Building |Others | |Area | |- |Computer Shop |Electronics | |Point | |- |Condominium |Organization/Association |Others |Area | |- |Covered Court |Sports Court | |Point | |- |Dental Clinic |Doctor/Clinic | |Point | |- |Diagnostic Clinic/Laboratory |Office | |Point | |- |Facial Care (not Dermatologist) |Personal Care | |Point | |- |Funeral Parlor/Memorial Chapel |Others | |Point | |- |Geothermal Plant |Industry | |Area | |- |Government Housing Project |Others; Government | |Area | |- |Health Center |Doctor/Clinic |Government |Point | |- |Home for the Aged |Organization/Association | |Point (may be Area if large enough) |*Add Government if applicable |- |Laundry Shop |Laundry/Dry Clean | |Point | |- |LPG Dealer |Shopping and Services | |Point | |- |Lying-in Clinic |Hospital/Urgent Care | |Point | |- |Mall |Shopping center | |Area | |- |Massage Center |Personal Care | |Point | |- |Medical Clinic |Doctor/Clinic | |Point | |- |Mosque |Religious Center | |Point (may be Area if large enough) | |- |Multi-use Buildings |Other | |Point (may be Area if large enough) |*May or may not tweak categories based on building use, e.g. as Lodging |- |Municipal Hall |City Hall | |Point (may be Area if large enough) | |- |Orphanage |Organization/Association | |Point |*Add Government if applicable |- |Pawnshop |Shopping and Services | |Point (may be Area if large enough) | |- |Pedestrian Footbridge |N/A | |DO NOT MAP | |- |Power Plant |Industry | |Area | |- |Private Pool/Resort |Swimming Pool |Lodging |Point (may be Area if Landmark) |*POOL and SWIMMING POOL ARE DIFFERENT |- |Provincial Capitol |City Hall | |Point (may be Area if large enough) | |- |Repair Shop |*whichever is applicable: car repair = car services, computer repair = electronics | |Point | |- |Rice Mill |Other | |Point (may be Area if large enough) | |- |Rural Health Unit |Hospital/Urgent Care |Government |Point | |- |Sari-Sari stores |Convenience Store | |Point (may be Area if large enough) | |- |Salon/Barber Shop |Personal Care | |Point | |- |Spa |Personal Care | |Point | |- |Subdivision/Village |Organization/Association |Others |Area | |- |Surgical Center |Doctor/Clinic | |Point | |- |Tattoo Studio/Parlor |Personal Care | |Point | |- |Temple |Religious Center | |Point (may be Area if large enough) | |- |Wet & Dry Market |Market | |Area | |- |Wind Farm |Industry | |Area | |- |Women's Center |Organization/Association | |Point (may be Area if large enough) |*Add Government if applicable |} 9b1c86260a1f0e8abe14564705323e57985ae214 0 6 10499 10480 2017-09-28T10:11:11Z Adabadada 39 Changed roster of LCs and AMs wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e.. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ and Country Coordinator</u> * kazmuth * SpeedDzel <u>Country Manager</u> * Baldugaras <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Adabadada * Lu_Wei_Jie * rccoros * jojob333 * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Manager/Global Champ |6 |- |SpeedDzel |Philippines |Country Manager/Global Champ |6 |- |Baldugaras |Philippines |Country Manager |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |5 |- |Adabadada |Philippines |Local Champ |5 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Southern Luzon |Local Champ |4 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR/Region 3 |Area Manager |4 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Region 4A |Area Manager |3 |- |Mondskiez |Mindanao |Area Manager |3 |- |jojob333 |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |3 |- |SuperBisdak |Region 10 |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 7705899da10934041a4047e93b05fb4be9e5e685 10528 10499 2019-06-15T18:19:05Z Adabadada 39 Updated list of champs and levels wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == The community in each country is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users, who also contribute to discussions on the forum. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participating in both the global and local Champs' groups, and being in a direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans which are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Lu_Wei_Jie * rccoros * jojob333 * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Southern Luzon |Local Champ |4 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR/Region 3 |Area Manager |5 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |jojob333 |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] f2095265a4c13b5420cf223c3eee6ff98eb2f9a0 10529 10528 2019-06-15T18:37:37Z Adabadada 39 /* Philippine Waze Champs and Experts */ wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Lu_Wei_Jie * rccoros * jojob333 * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly. *Make changes to the map when road geometry needs to be changed, or roads added or removed from the map. *Edit road construction areas, especially for closures so that users are not routed into those areas. *Respond to and act on Update Requests from Waze drivers. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. *Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map. By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Southern Luzon |Local Champ |4 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR/Region 3 |Area Manager |5 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |jojob333 |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 3e94411fe787a6943758117d827e60bc0a33b30e 10530 10529 2019-06-15T18:50:39Z Adabadada 39 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Lu_Wei_Jie * rccoros * jojob333 * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include but are not necessarily limited to: #Seek to continuously improve the maps for navigation, i.e. naming unnamed roads and setting turns properly #Make changes to the map when road geometry needs to be changed, or when roads need to be added/removed from the map #Edit road closures so that users are not routed through those areas. #Respond to and act on Update Requests from Waze drivers. #Maintain speed and red-light cameras, process reports of devices from Waze drivers. #Process and resolve Map Errors or Problems in the Waze Map Editor. #Act as a mentor to other editors, offering advice in the forums and whenever improper edits are spotted on the map #By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Southern Luzon |Local Champ |4 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR/Region 3 |Area Manager |5 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |jojob333 |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 8e82d92b3dac09086285ee67cb84ab96cdb3c552 0 14 10512 10476 2018-06-29T03:18:17Z Kazmuth 35 wikitext text/x-wiki __TOC__ *'''Here are the most asked questions from Pinoy Waze Editors''' ==Is there a manual for Waze map editing?== There is a [[global:Waze_Map_Editor|Waze Map Editor]] manual that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [[Philippines/Editing resources |Editing Resources for the Philippines]] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed on our guide are specifically for our pinoy roads and driving habits. ==I've been blocked and I can't edit on WME or send a report through the app== If you have received a message on the app or an email notification that you have been blocked, this is because of either 1. You have been detected by the Waze system as massively reporting. or 2. You have been reported by the community because you are violating the rules imposed by Waze and/or the community. If #1 is the case, even if we could, we will not help you with this. Like Waze, we do not tolerate cheating, and will not lift a finger to help you get unblocked or unbanned. By spamming the reports function you intentionally send out wrong, inconsistent, spurious, or unneeded data. You are also skewing the data being collected by Waze making the aggregate data inaccurate. If you fall under #2 then what you should do is 1. Read the wiki, particularly the [[Philippines]] section so you can figure out what you did wrong 2. Join the [https://www.facebook.com/groups/WazePhilippines/ Waze Philippines FB Group] 3. Join the [https://t.me/joinchat/AgCmlz-Od3TyzFma6EuoTA Waze Philippines Telegram channel] 4. Post a message on the FB group or the Telegram channel and tell us your predicament. If you fail to read the wiki and figure out why you were blocked, we will not help you. ==Why am I not leveling up to Level 2 or 3?== We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]), have joined at least 1 [[Philippines/MapRaid_History|PH MapRaid]], have attended the "Intro to Map Editing Webinar", and have joined the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg PH Telegram channel]. This means all Waze editors will be force-ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. ''New Area Managers are also not automatically promoted to Level 3 and will remain at their level until the local champs agree to promote based on the quality of edits''. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] ==How do I apply to be an Area Manager?== To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[global:Area_Manager|Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] ==How long does it take until my edits gets displayed on my Waze app?== It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://wazestatus.wordpress.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area ==When I encounter traffic on the road, what type do I report?== You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph ==I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?== The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are '''NO ROADS''' which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, and most Expressways. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps because of report abuse. You will still be able to report them but they will no longer appear on WME and you will not get any points for them. ==What is the difference between Map Problems and Update Requests?== Map Problems or MPs are Waze generated and based on analyzed Wazer traffic. Update Requests or URs are Waze user submitted requests to fix user identified map issues. ==How do I fix Map Problems?== Visit the [[global:Map_Problems_in_Waze_Map_Editor|Map Problem]] wiki for more details. ==How do I fix Update Requests?== Visit the [[global:Update_Requests_in_Waze_Map_Editor|Update Requests]] wiki for more details. ==Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?== On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. ==Waze does not use the U-Turn segment I created between two roads, what could be the problem?== Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. ==Are there any shortcut keys for the Waze Map Editor?== You can view the wiki page on [[global:Keyboard_shortcuts|Keyboard shortcuts]] ==Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?== Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. ==I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?== You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. ==The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?== The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. ==There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?== You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the Partial[[global:Partial_restrictions| restrictions]] wiki. ==Search function doesn't work, how do I fix it?== This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. ==I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?== If refreshing the map editor does not work, go to [http://status.waze.com the Waze status page] and check for any announcement from Waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==How do I report flooding so that Wazers will not be routed on a flooded road?== Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report an unpassable road due to flooding, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank, and the country. *The road will be opened when Waze detects that a number of users have driven through the road. [[Category:Philippines]] 3bd010b804f863ec835153d701083a4846debc2a 10520 10512 2019-04-29T08:24:27Z Rccoros 5 /* How long does it take until my edits gets displayed on my Waze app? */ Updated url for Waze Status wikitext text/x-wiki __TOC__ *'''Here are the most asked questions from Pinoy Waze Editors''' ==Is there a manual for Waze map editing?== There is a [[global:Waze_Map_Editor|Waze Map Editor]] manual that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads. A Map Editing Guide for the Philippines is available in the [[Philippines/Editing resources |Editing Resources for the Philippines]] and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the [[global:Best_map_editing_practice|Best map editing practice]] guide in the wiki. However, some items listed on our guide are specifically for our pinoy roads and driving habits. ==I've been blocked and I can't edit on WME or send a report through the app== If you have received a message on the app or an email notification that you have been blocked, this is because of either 1. You have been detected by the Waze system as massively reporting. or 2. You have been reported by the community because you are violating the rules imposed by Waze and/or the community. If #1 is the case, even if we could, we will not help you with this. Like Waze, we do not tolerate cheating, and will not lift a finger to help you get unblocked or unbanned. By spamming the reports function you intentionally send out wrong, inconsistent, spurious, or unneeded data. You are also skewing the data being collected by Waze making the aggregate data inaccurate. If you fall under #2 then what you should do is 1. Read the wiki, particularly the [[Philippines]] section so you can figure out what you did wrong 2. Join the [https://www.facebook.com/groups/WazePhilippines/ Waze Philippines FB Group] 3. Join the [https://t.me/joinchat/AgCmlz-Od3TyzFma6EuoTA Waze Philippines Telegram channel] 4. Post a message on the FB group or the Telegram channel and tell us your predicament. If you fail to read the wiki and figure out why you were blocked, we will not help you. ==Why am I not leveling up to Level 2 or 3?== We have implemented a policy which will limit Level 3 to senior Area Managers and Level 2 to those in contact with the local community (member of the [https://www.facebook.com/groups/WazePhilippines/ PH FB group] or active on the [http://world.waze.com/forum/viewforum.php?f=309 Waze PH Forum]), have joined at least 1 [[Philippines/MapRaid_History|PH MapRaid]], have attended the "Intro to Map Editing Webinar", and have joined the [https://t.me/joinchat/AAAAAD-Od3TbOGotNej5Fg PH Telegram channel]. This means all Waze editors will be force-ranked and will remain at Level 1 regardless of their map edit count unless they apply for a level upgrade and get approved. ''New Area Managers are also not automatically promoted to Level 3 and will remain at their level until the local champs agree to promote based on the quality of edits''. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum. You can apply for a level upgrade if you meet the requirements set by the PH community. Please use the [https://docs.google.com/forms/d/17mlBDW-tJZ2Z4xAX7hIgk02hFr6YDPPbj7wGuaWZxPM/viewform?usp=send_form Waze Philippines Level Upgrade Application Form] ==How do I apply to be an Area Manager?== To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dGpGdTZicXpJalpBSTdvRGEtU0pTd0E6MA#gid=0 Philippine Waze area-management request form] and submit. There is also a wiki page on [[global:Area_Manager|Area Manager]]. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs To view the requirements for an Area Manager, please check out the [[Philippines/Champs_And_AMs|Philippine Champs and Area Managers wiki]] ==How long does it take until my edits gets displayed on my Waze app?== It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out [https://status.waze.com/ waze status page] for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area ==When I encounter traffic on the road, what type do I report?== You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. You do not need to submit a traffic condition for all roads if they are not highlighted by a traffic condition. Traffic condition highlights are purely visual and does not affect the routing. Repeatedly reporting traffic might lead to your account getting blocked and your points stripped due to report spamming (also considered cheating). If you would still like to report traffic, here are the traffic types; '''Standstill traffic''' - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection) '''Heavy traffic''' - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving. '''Moderate traffic''' - Speed is usually 10 to 25 kph ==I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?== The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are '''NO ROADS''' which have fixed or static speed cams. What we have are mobile speed cameras and these are located on Commonwealth Ave, Macapagal Blvd, and most Expressways. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions. As of 6/19/2014, speedcameras have been disabled on our maps because of report abuse. You will still be able to report them but they will no longer appear on WME and you will not get any points for them. ==What is the difference between Map Problems and Update Requests?== Map Problems or MPs are Waze generated and based on analyzed Wazer traffic. Update Requests or URs are Waze user submitted requests to fix user identified map issues. ==How do I fix Map Problems?== Visit the [[global:Map_Problems_in_Waze_Map_Editor|Map Problem]] wiki for more details. ==How do I fix Update Requests?== Visit the [[global:Update_Requests_in_Waze_Map_Editor|Update Requests]] wiki for more details. ==Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this?== On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment. ==Waze does not use the U-Turn segment I created between two roads, what could be the problem?== Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters. ==Are there any shortcut keys for the Waze Map Editor?== You can view the wiki page on [[global:Keyboard_shortcuts|Keyboard shortcuts]] ==Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?== Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision. ==I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?== You can request for an unlock in the [http://world.waze.com/forum/viewforum.php?f=309 Philippines - Waze Forum] or in the [https://www.facebook.com/groups/WazePhilippines/ Philippine Waze Users Facebook Group]. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions. ==The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?== The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears. ==There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?== You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the Partial[[global:Partial_restrictions| restrictions]] wiki. ==Search function doesn't work, how do I fix it?== This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device. ==I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?== If refreshing the map editor does not work, go to [http://status.waze.com the Waze status page] and check for any announcement from Waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later). ==How do I report flooding so that Wazers will not be routed on a flooded road?== Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report. To report an unpassable road due to flooding, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send. Notes: *If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure. *The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank, and the country. *The road will be opened when Waze detects that a number of users have driven through the road. [[Category:Philippines]] 865e4aa7c37b27dfd6a3d6a9bd1db5356b7af84b 2 19 10519 2019-03-13T11:52:45Z Rccoros 5 Created page with "I am a Level 5 Editor. Local Champ WME Beta Tester Android App Beta tester" wikitext text/x-wiki I am a Level 5 Editor. Local Champ WME Beta Tester Android App Beta tester 19f595f797f849ec0c7012f992f95958a1c7c937 0 2 10531 10511 2019-07-20T05:57:49Z Rccoros 5 Fixed link to Best Map editing practice wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[global:Best_map_editing_practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain and update the area where they live. This means, L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc. # Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues. # Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. == General Guidelines on Road Editing == 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" except if it will immediately fork into two exits. Or the exit leads to two separate turns # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit'. Segment names are not localized so it will sound awkward when the rest of the instructions are in Filipino. # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == General Guidelines on Editing Places == Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination == General Guidelines on other WME Objects == === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. If you need to set an RTC that is more than a month long, make sure you check on it at least once a week. There have been a lot of instances where RTCs for several months have been placed and then never checked again. This resulted in segments being closed off from routing long after they have reopened. URs were piling up on the area due to this and routing has been severely affected on the area. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === Adding any form of camera from the app has been disabled. This can only be added on WME by high level editors. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] fb04d52d53816e19e79e062784e00705e781affc 10532 10531 2019-07-20T05:58:17Z Rccoros 5 /* General Guidelines on Road Editing */ wikitext text/x-wiki == Map Editing Guide for the Philippines == It is presumed you have read [[global:Best_map_editing_practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' === Note to all would-be editors in the Philippines === Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. === Map Editing Priorities === Higher level editors especially Area Managers, are expected to maintain and update the area where they live. This means, L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs. The suggested way to clear your area is; # Go to maximum zoom in level (10) # Go to your location # Zoom out one level at a time # Resolve and UR, MP, PUR, etc. # Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' # Update Requests - Do this first to reduce the number of URs. # Place Update Requests - Do this next if you have cleared ALL URs. # System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues. # Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations. '''The following are NOT priorities, work on the previous list instead of these:''' # Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. # Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. == General Guidelines on Road Editing == 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[global:Best_map_editing_practice|Best map editing practice]] for specifics. 2. Setting the road type: * Freeways – Toll Roads or Expressways where a toll fee needs to be paid * Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels * Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population * Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. * Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads * Street – ordinary street, mainly residential * Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. * Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. * Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. * Ferry - Ferries that meet any of these conditions should generally not be mapped ** Passenger ferries without vehicles ** Ferries requiring pre-booking ** Private ferries unavailable to the general public ** Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map * Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: * Toll Road - Expressways where toll fees are collected * Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through * Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - # Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]). # Do not use multiple street names separated with a slash "/" except if it will immediately fork into two exits. Or the exit leads to two separate turns # If there are local (LGU) or other name for the street, add them as an alternative name # Use punctuation for initials except for cardinal directions # N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions # Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) # Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS # Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit'. Segment names are not localized so it will sound awkward when the rest of the instructions are in Filipino. # Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. * Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. * U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: * There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a driver side turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: * When the turn lane physically separates from the main road well in advance of the intersection * When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation * When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier * When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector * When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane * When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. == General Guidelines on Editing Places == Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. * '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination == General Guidelines on other WME Objects == === Map Comments === Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. === Real Time Closures === A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. If you need to set an RTC that is more than a month long, make sure you check on it at least once a week. There have been a lot of instances where RTCs for several months have been placed and then never checked again. This resulted in segments being closed off from routing long after they have reopened. URs were piling up on the area due to this and routing has been severely affected on the area. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras === Adding any form of camera from the app has been disabled. This can only be added on WME by high level editors. === Major Traffic Events === A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. === Subdivisions, Villages, Gated, Restricted, and Private Compounds === In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] f1766b8f03981765f6a1fc1d33f7bb5c5d13f566 10542 10532 2021-04-14T14:25:46Z Tilonius 93 /* General Guidelines on Road Editing */ linkt to DPWH corrected wikitext text/x-wiki ==Map Editing Guide for the Philippines== It is presumed you have read [[global:Best_map_editing_practice|Best map editing practice]] before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. '''''This supersedes any generic guide wiki entries not specific to the Philippines.''''' ===Note to all would-be editors in the Philippines=== Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines. ===Map Editing Priorities=== Higher level editors especially Area Managers, are expected to maintain and update the area where they live. This means, L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs. The suggested way to clear your area is; #Go to maximum zoom in level (10) #Go to your location #Zoom out one level at a time #Resolve and UR, MP, PUR, etc. #Repeat step 3 and 4 By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:''' #Update Requests - Do this first to reduce the number of URs. #Place Update Requests - Do this next if you have cleared ALL URs. #System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues. #Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations. '''The following are NOT priorities, work on the previous list instead of these:''' #Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions. #Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. #Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. ==General Guidelines on Road Editing== 1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See [[global:Best_map_editing_practice|Best map editing practice]] for specifics. 2. Setting the road type: *Freeways – Toll Roads or Expressways where a toll fee needs to be paid *Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels *Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population *Minor Highway – DPWH Secondary Roads or roads that connect other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network. *Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads *Street – ordinary street, mainly residential *Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. *Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area. *Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required. *Ferry - Ferries that meet any of these conditions should generally not be mapped **Passenger ferries without vehicles **Ferries requiring pre-booking **Private ferries unavailable to the general public **Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map *Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it. 3. Setting road type attributes: *Toll Road - Expressways where toll fees are collected *Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through *Tunnel - If the road is underground 4. Setting directionality: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two-way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level unless they pass under a segment already on ground level. 6. Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 (Section 35) ''Restriction as to speed''. Check [[Philippines/Speedlimit|here]] for details. 7. Connecting or creating junctions (attaching to existing roads): Before attempting to connect roads, make sure both roads are within your editing level. If any segment is above your level you will not be able to make a connection (they are not connected even if they look like they are). All you will have succeeded in doing was to put an end node on top of a segment. You will know that you have successfully made a connection/junction when you see the roads "snap" together, and turn direction arrows appear. Do not make a connection/junction between non-routable road types (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems. 8. Setting turn restrictions and u-turns on junctions: This is straightforward - red is disallowed, green is allowed. The easiest and fastest way to allow all turns is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. For u-turns at junctions (those fish-hook u turns at the ends of segments), the default is still to leave them disabled. 9. Naming roads: If you don't know the street name, add the city name and mark the street name as 'None'. Somebody else could edit it. '''Do not''' leave segments in red (unnamed). '''Do not''' name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout. Follow the PH Road Naming convention when adding road names - #Always use the official name as the street name [https://www.dpwh.gov.ph/DPWH/gis/rbi (DPWH Name]). #Do not use multiple street names separated with a slash "/" except if it will immediately fork into two exits. Or the exit leads to two separate turns #If there are local (LGU) or other name for the street, add them as an alternative name #Use punctuation for initials except for cardinal directions #N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions #Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name) #Do not use the word 'to' (preposition) on a street name, unless it is an actual street name. It will not sound right when using 'Adora' or non English TTS #Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit'. Segment names are not localized so it will sound awkward when the rest of the instructions are in Filipino. #Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki> 10. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech). '''The City field should only contain the CITY or MUNICIPAL Name and NOT the AREA''''', '''''SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.''' Take extra care on the '''City''' labels of your edits. Unlike '''Street''' names which reflects edits (or corrections) quicker and appears on the next update, City names embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client app despite any corrections made. Stick to the '''official''' (but shortest possible) name of the jurisdiction being edited. If you are unsure of the political boundaries of the '''"city"''' you are editing, ''leave it'' at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out. On the matter of city labels, we omit the word "city" to derive the shortest possible official political name of the area. The only exceptions are ''Quezon, Cebu, Davao, Cavite'', etc as these cities have a provincial counterpart. This will distinguish ''Quezon City'' with the province of ''Quezon'', ''Cebu City'' with the province of ''Cebu'', and so on. All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name. Currently Waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for ''Laguna'', Alaminos (P) for ''Pangasinan''. Kindly refer to this link of '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines. 11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''Do not split roads unless''' they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain. Some formal guidelines for splitting roads in the Philippines A road '''should be split''' if: *GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level. *Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage. *U-Turns are required to properly make turns that are blocked by a median. A road '''should not''' '''be split''' because: *There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable (see exceptions above). *The non-drivable median is interrupted by a cross segment at most intersections. *There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. *It is possible and legal to make a driver side turn/u-turn everywhere along the road *The objective is solely for visual appearance or to make the road match another visual source like Google Maps. 12. Turn Lanes or at-grade connectors: First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector *When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane *When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc 13. Locking roads: When you are confident of the area you have mapped, '''lock the roads''' to prevent any changes or edits on the roads. While we appreciate the help of newbie Waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the [[Philippines/Locking |Philippines Locking Policy]] for more details. 14. '''KISS! - Keep It Simple, Stupid'''! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided. ==General Guidelines on Editing Places== Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details. *'''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . *'''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination ==General Guidelines on other WME Objects== ===Map Comments=== Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook. See next section for guidance on use of Map Comments with Real Time Closures. ===Real Time Closures=== A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that. If you need to set an RTC that is more than a month long, make sure you check on it at least once a week. There have been a lot of instances where RTCs for several months have been placed and then never checked again. This resulted in segments being closed off from routing long after they have reopened. URs were piling up on the area due to this and routing has been severely affected on the area. Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. ===Speed Cameras=== Adding any form of camera from the app has been disabled. This can only be added on WME by high level editors. ===Major Traffic Events=== A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details. Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly. ===Subdivisions, Villages, Gated, Restricted, and Private Compounds=== In order to not break routing into gated areas, all roads inside these areas should be of the Private road type. If there are multiple entrances to these areas, consider implementing suggestions from the [[global:Private_Installations|Private Installations]] wiki. If you are unsure how to do this, contact your area manager or a senior editor. [[Category:Philippines]] 6c9054fcaf979342b81e5b3482dc78e6c39f5a01 0 6 10533 10530 2019-07-20T06:00:15Z Rccoros 5 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Lu_Wei_Jie * rccoros * jojob333 * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include but are not necessarily limited to: #Seek to continuously improve the maps for navigation, i.e. naming unnamed roads and setting turns properly #Make changes to the map when road geometry needs to be changed, or when roads need to be added/removed from the map #Edit road closures so that users are not routed through those areas. #Respond to and act on Update Requests from Waze drivers. #Maintain speed and red-light cameras, process reports of devices from Waze drivers. #Process and resolve Map Errors or Problems in the Waze Map Editor. #Act as a mentor to other editors, offering advice in the forums and whenever improper edits are spotted on the map #By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Region IV-A, V |Local Champ |4 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |NCR/Region 3 |Area Manager |5 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |jojob333 |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 329cfb2b73a4ea8f9dada967e094b2a668bac9f5 10534 10533 2019-07-20T06:03:54Z Rccoros 5 /* Philippine Waze Area Manager */ wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Lu_Wei_Jie * rccoros * jojob333 * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include but are not necessarily limited to: #Seek to continuously improve the maps for navigation, i.e. naming unnamed roads and setting turns properly #Make changes to the map when road geometry needs to be changed, or when roads need to be added/removed from the map #Edit road closures so that users are not routed through those areas. #Respond to and act on Update Requests from Waze drivers. #Maintain speed and red-light cameras, process reports of devices from Waze drivers. #Process and resolve Map Errors or Problems in the Waze Map Editor. #Act as a mentor to other editors, offering advice in the forums and whenever improper edits are spotted on the map #By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Region IV-A, V |Local Champ |4 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |Philippines |Local Champ |5 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |jojob333 |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 7c96cf585d076280f40571419a371c53a9a79fea 10539 10534 2020-05-05T11:22:58Z Rccoros 5 updated name for glychlor wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Lu_Wei_Jie * rccoros * glychlor * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include but are not necessarily limited to: #Seek to continuously improve the maps for navigation, i.e. naming unnamed roads and setting turns properly #Make changes to the map when road geometry needs to be changed, or when roads need to be added/removed from the map #Edit road closures so that users are not routed through those areas. #Respond to and act on Update Requests from Waze drivers. #Maintain speed and red-light cameras, process reports of devices from Waze drivers. #Process and resolve Map Errors or Problems in the Waze Map Editor. #Act as a mentor to other editors, offering advice in the forums and whenever improper edits are spotted on the map #By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Region IV-A, V |Local Champ |4 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | Dekca | Pampanga |Area Manager |3 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |Philippines |Local Champ |5 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |glychlor |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 7a82a9e834d13ceab5b48de2ad13b778c0a5d6aa 10540 10539 2020-05-05T11:24:10Z Rccoros 5 wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Lu_Wei_Jie * rccoros * glychlor * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include but are not necessarily limited to: #Seek to continuously improve the maps for navigation, i.e. naming unnamed roads and setting turns properly #Make changes to the map when road geometry needs to be changed, or when roads need to be added/removed from the map #Edit road closures so that users are not routed through those areas. #Respond to and act on Update Requests from Waze drivers. #Maintain speed and red-light cameras, process reports of devices from Waze drivers. #Process and resolve Map Errors or Problems in the Waze Map Editor. #Act as a mentor to other editors, offering advice in the forums and whenever improper edits are spotted on the map #By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |NCR/Region IV-A, V |Local Champ |4 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | rock_stone | Cebu Province |Area Manager |3 |- |Brezzypete |Philippines |Local Champ |5 |- |XMapperMG |Mindanao |Area Manager |4 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |glychlor |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] eec97da5c3cc30962f714ffbf76df63bae0c805b 10543 10540 2022-11-30T12:58:11Z Rccoros 5 Updated level of some editors. Also removed XMapperMG from the list wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Lu_Wei_Jie * rccoros * glychlor * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include but are not necessarily limited to: #Seek to continuously improve the maps for navigation, i.e. naming unnamed roads and setting turns properly #Make changes to the map when road geometry needs to be changed, or when roads need to be added/removed from the map #Edit road closures so that users are not routed through those areas. #Respond to and act on Update Requests from Waze drivers. #Maintain speed and red-light cameras, process reports of devices from Waze drivers. #Process and resolve Map Errors or Problems in the Waze Map Editor. #Act as a mentor to other editors, offering advice in the forums and whenever improper edits are spotted on the map #By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Northern Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |Philippines |Local Champ |5 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- | rock_stone | Cebu Province |Area Manager |4 |- |Brezzypete |Philippines |Local Champ |5 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |glychlor |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 7e48c8348194c7a5c5472787475d377978ec2a7a 10546 10543 2023-03-21T04:56:16Z Rccoros 5 wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Baldugaras * Lu_Wei_Jie * rccoros * glychlor * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include but are not necessarily limited to: #Seek to continuously improve the maps for navigation, i.e. naming unnamed roads and setting turns properly #Make changes to the map when road geometry needs to be changed, or when roads need to be added/removed from the map #Edit road closures so that users are not routed through those areas. #Respond to and act on Update Requests from Waze drivers. #Maintain speed and red-light cameras, process reports of devices from Waze drivers. #Process and resolve Map Errors or Problems in the Waze Map Editor. #Act as a mentor to other editors, offering advice in the forums and whenever improper edits are spotted on the map #By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |Philippines |Local Champ |5 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- |rock_stone |Cebu Province |Area Manager |4 |- |Brezzypete |Philippines |Local Champ |5 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |glychlor |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |- |ceclimaco |NCR/Region 4A |Area Manager |4 |- |EdB971129 |NCR/Region 4A |Area Manager |2 |- |Litterbug2 |North Luzon |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] a7de7ec7ec1feb12a608dcb126fd8c1e11ec8040 10549 10546 2023-04-07T09:51:36Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Lu_Wei_Jie * rccoros * glychlor * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include but are not necessarily limited to: #Seek to continuously improve the maps for navigation, i.e. naming unnamed roads and setting turns properly #Make changes to the map when road geometry needs to be changed, or when roads need to be added/removed from the map #Edit road closures so that users are not routed through those areas. #Respond to and act on Update Requests from Waze drivers. #Maintain speed and red-light cameras, process reports of devices from Waze drivers. #Process and resolve Map Errors or Problems in the Waze Map Editor. #Act as a mentor to other editors, offering advice in the forums and whenever improper edits are spotted on the map #By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Baldugaras |Philippines |Local Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |Philippines |Local Champ |5 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- |rock_stone |Cebu Province |Area Manager |4 |- |Brezzypete |Philippines |Local Champ |5 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |glychlor |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |- |ceclimaco |NCR/Region 4A |Area Manager |4 |- |EdB971129 |NCR/Region 4A |Area Manager |2 |- |Litterbug2 |North Luzon |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 560da115a9540835a8ecc5c9a5bd3ea4d77965cb 10550 10549 2023-04-07T09:54:08Z Kazmuth 35 wikitext text/x-wiki __TOC__ == Philippine Waze Champs and Experts == In every country, the community is Waze’s beating heart. It edits the map, helps with localization and provides Waze with important info and feedback. Each community is a little different, but there are common roles and rules that are relevant to everyone. '''Champs are the community leaders''' <br /> Champs are the most experienced users who also contribute to discussions on the forum or the community's Facebook page. This is not just about editing skills - it’s about actively participating in the community. Global champ - Part of the world community leadership of Waze Local champ - Part of a specific country’s community leadership Coordinators are users (usually Champs) who act as the community’s ambassadors to Waze. They have a direct communication channel to the company. '''A Coordinator’s main responsibilities:''' <br /> Participate in both the global and local Champs' groups, and be in direct contact with the relevant Waze community manager Advise about the urgency and the severity of any reported issue Be aware of the company news, product announcements, new versions etc. Take part in the setup of local and regional editors meetups Experts are editors who've mastered a certain field - be it Routing, Android, iOS or localization Experts are the ‘top-authority’ for anything related to their expertise Experts will be part of the global experts group and will work closely with Waze and with community members Waze will share with the group of experts all sorts of professional information, knowledge and future plans that are relevant for their area of expertise. Experts will be responsible to ‘carry & deliver’ the relevant information to the local community. Experts Will moderate relevant forums and will manage relevant Wiki pages Country and Division Managers are Champs who take charge of the entire country or several states/counties in large countries, i.e. provinces/regions for the Philippines. They manage a region in all things relevant to the community Division Managers are added according to the community’s judgement, usually in large countries, in which geographic limitations require another layer of community involvement. <u>Global Champ</u> * kazmuth * SpeedDzel * Adabadada <u>Local Champs</u> * zy_pher * Guardian4ngel * shogsbro * Lu_Wei_Jie * rccoros * glychlor * Brezzypete <u>Wiki Masters</u> * kazmuth * Adabadada <u>Localization Team</u> * Adabadada (Language Coordinator) * kazmuth * MrsEarth18 * SpeedDzel * rccoros * Lukring == Philippine Waze Area Manager == '''What is an Area Manager and what does it entail:''' *An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include but are not necessarily limited to: #Seek to continuously improve the maps for navigation, i.e. naming unnamed roads and setting turns properly #Make changes to the map when road geometry needs to be changed, or when roads need to be added/removed from the map #Edit road closures so that users are not routed through those areas. #Respond to and act on Update Requests from Waze drivers. #Maintain speed and red-light cameras, process reports of devices from Waze drivers. #Process and resolve Map Errors or Problems in the Waze Map Editor. #Act as a mentor to other editors, offering advice in the forums and whenever improper edits are spotted on the map #By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above. When you become inactive or unreachable for 90 days, your AM permissions and level will be revoked. <br/><u>'''The following are the conditions or requirements for approval of AM applications:'''</u> *Approval of at least <span style="color:#ff0000;">'''3&nbsp;'''</span>current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant. *Meets '<span style="color:#ff0000;">'''X'''</span>' number of edits for area applied **City wide or permalink wide - <span style="color:#ff0000;">'''10k&nbsp;'''</span>map edits **Metro Manila, Metro Cebu, & Metro Davao wide - <span style="color:#ff0000;">'''20k&nbsp;'''</span>map edits **Province wide - '''<span style="color:#ff0000;">25k&nbsp;</span>'''map edits **Region wide - '''<span style="color:#ff0000;">50k&nbsp;</span>'''map edits **Luzon, Visayas, or Mindanao Island Groups - <span style="color:#ff0000;">'''100k&nbsp;'''</span>map edits **Countrywide - CM only or 250k edits *Must have at least <span style="color:#ff0000;">'''10&nbsp;'''</span>posts in Waze forum or FB group page (must be related to waze and have sense) *Must have resolved at least <span style="color:#ff0000;">'''100&nbsp;'''</span>update requests *Must have at least '''<span style="color:#ff0000;">2,500</span>''' existing kilometers *Must be an active member of the [https://www.waze.com/forum/viewforum.php?f=309 <i>Philippine Waze forum</i>] and/or [https://www.facebook.com/groups/WazePhilippines/ <i>FB group page</i>] *Must attend at least <span style="color:#ff0000;">'''1&nbsp;'''</span>waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila *Must ''pass ''an online exam. (Currently under process) <br/>'''List of Philippines Area Managers''' You may send these wazers a message in the forums if you want to have an issue fixed in their respective areas. {| class="wikitable sortable" border="3" style="margin-left: 3em;text-align: center" |- style="background: silver" ! scope="col" | Waze Username ! scope="col" | Area !COMMENTS !LEVEL |- |kazmuth |Philippines |Country Coordinator/Global Champ |6 |- |SpeedDzel |Philippines |Country Coordinator/Global Champ |6 |- |Lu_Wei_Jie |Philippines |Local Champ |5 |- |zy_pher |Philippines |Local Champ |6 |- |Adabadada |Philippines |Global Champ |6 |- |shogsbro |Luzon/UAE |Local Champ |5 |- |Guardian4ngel |Luzon/Singapore |Local Champ/Country Manager for SG/Global Champ |6 |- |rccoros |Philippines |Local Champ |5 |- |deadlockprocess |Philippines |Area Manager |5 |- |iceden |Philippines |Area Manager |4 |- |Ungas |Region IV-A, V |Area Manager |4 |- |rock_stone |Cebu Province |Area Manager |4 |- |Brezzypete |Philippines |Local Champ |5 |- |Lukring |NCR/Region 4A |Area Manager |4 |- |Mondskiez |Mindanao |Area Manager |3 |- |glychlor |NCR/Region 4A |Local Champ |4 |- |kabutengkamote |Cavite/Qatar |Area Manager |4 |- |SuperBisdak |Region 10 |Area Manager |3 |- |ceclimaco |NCR/Region 4A |Area Manager |4 |- |EdB971129 |NCR/Region 4A |Area Manager |2 |- |Litterbug2 |North Luzon |Area Manager |3 |} '''Note: Even though approved as an area manager, management for an assigned area will be lost after three months of inactivity or Waze editing.''' [[Category:Philippines]] 6dfb7d81c943cf1612da21b0da91b63e242937be 0 17 10535 10522 2019-07-20T06:09:44Z Rccoros 5 /* 2019 */ wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 3-5, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''June 30 - July 2, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines '''December 1 - 2, 2017: Waze APAC Regional Meetup 2017 '''<br /> Venue: Pullman Bangkok King Power, Thailand == 2018 == '''April 13 - 15, 2018: Waze APAC Mega Regional Meetup <br />''' Venue: ParkRoyal on Pickering, Singapore May 27, 2018: Southies Meetup <br /> Venue: Bawai’s Vietnamese Kitchen, Nuvali '''Aug. 18, 2018: Third National Meetup <br />''' Venue: Crowne Plaza Manila, Philippines '''October 12 - 14, 2018: BetaLization Meetup <br />''' Venue: Courtyard by Marriott Berlin City Center, Germany == 2019 == February 3, 2019: Waze Cafe Venue: UP Diliman '''April 12 - 14, 2019: Waze APAC Mega Regional Meetup <br />''' Venue: Pullman Bangkok King Power, Thailand April 19, 2019: Holy Week at BGC <br /> Venue: Pink's Hot Dogs May 25, 2019: Waze Cafe <br /> Venue: Spiral June 8, 2019: Mapraid <br /> Venue: Google Office, BGC 0f6f525b3ace429e8a4fc6ee3852dd3210c6cb46 10547 10535 2023-03-22T12:35:58Z Rccoros 5 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 3-5, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''June 30 - July 2, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines '''December 1 - 2, 2017: Waze APAC Regional Meetup 2017 '''<br /> Venue: Pullman Bangkok King Power, Thailand == 2018 == '''April 13 - 15, 2018: Waze APAC Mega Regional Meetup <br />''' Venue: ParkRoyal on Pickering, Singapore May 27, 2018: Southies Meetup <br /> Venue: Bawai’s Vietnamese Kitchen, Nuvali '''Aug. 18, 2018: Third National Meetup <br />''' Venue: Crowne Plaza Manila, Philippines '''October 12 - 14, 2018: BetaLization Meetup <br />''' Venue: Courtyard by Marriott Berlin City Center, Germany == 2019 == February 3, 2019: Waze Cafe Venue: UP Diliman '''April 12 - 14, 2019: Waze APAC Mega Regional Meetup <br />''' Venue: Pullman Bangkok King Power, Thailand April 19, 2019: Holy Week at BGC <br /> Venue: Pink's Hot Dogs May 25, 2019: Waze Cafe <br /> Venue: Spiral June 8, 2019: Mapraid <br /> Venue: Google Office, BGC == 2022 == '''November 18-19, 2022: APAC Mini Regional Meetup <br />''' Venue: Sheraton Manila, Philippines == 2023 == '''March 17 - 19, 2023: Waze APAC Mega Regional Meetup <br />''' Venue: Bangkok Marriott Marquis Queen’s Park, Thailand 899d1e80f11861af8db1fdb8d6feb057f79d03a1 10548 10547 2023-03-22T12:38:43Z Rccoros 5 Updated date for APAC Mini Regional 2022 wikitext text/x-wiki The Waze Philippines Community holds fairly frequent meetups, both official and unofficial, to talk about anything and everything Waze, or just to enjoy each others' company. Here is a brief timeline of all meetups held/attended by members of the community: == 2013 == '''June 8, 2013: First Local Meetup <br />''' Venue: Starbucks 32nd cor 7th Ave. BGC September 14, 2014: Second Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC Dec. 7, 2014: Third Meetup <br /> Venue: Starbucks 32nd cor 7th Ave. BGC == 2014 == March 15, 2014: Fourth Meetup<br /> Venue: Starbucks 32nd cor 7th Ave. BGC then moved to Gram's Diner, BGC '''June 14, 2014: First National Meetup <br />''' Venue: F1 Hotel, BGC''' October 18-19, 2014: Baguio Roadtrip <br /> Venue: The Arc, Baguio Dec. 4, 2014: First Cebu Meetup <br /> Venue: The Vue, Cebu Yacht Club == 2015 == Jan. 19, 2015: Meetup for all Wazers <br /> Venue: Gram's Diner, BGC Jan. 27, 2015: Editors' Dinner <br /> Venue: San Antonio Plaza, Makati Feb. 6, 2105: Dinner and Drinks for all Wazers<br /> Venue: Burger and Brewskies, BGC March 13, 2015: Editors' Dinner and Drinks <br /> Venue: Yakimix Prime; Chihuahua, BGC March 28, 2015: Wazers' Meetup <br /> Venue: Chihuahua, BGC June 12, 2015: First Go-kart Meetup <br /> Venue: CityKart Makati '''June 18-22, 2015: Second Global Meetup''' <br /> Venue: Intercontinental David, Tel Aviv July 2015: Meetings with Urban Land Institute Sept. 4, 2015: Editors' Dinner <br /> Venue: Puccini and Wildflour Sept. 25, 2015: Second Go-kart Meetup<br /> Venue: CityKart Makati '''Dec. 4-6, 2015: First SEA Regional Meetup <br /> Venue: Mandarin Oriental, Singapore''' Dec. 30, 2015: Post-Christmas Meetup <br /> Venue: Hanamaruken at The Grove == 2016 == '''March 3-5, 2016: First SEA Regional Beta Meetup <br />''' Venue: Mandarin Oriental, Singapore March 24, 2016: Holy Week at BGC <br /> Venue: 'Cue BHS, Jamba Juice BHS '''May 14, 2016: Waze Cafe - MapRaid Awards <br />''' Venue: Mona Lisa Ristorante, SM Aura'''<nowiki/>''' July 10, 2016: Editors' Dinner <br /> Venue: Puccini July 31, 2016: Meetup for all Wazers <br /> Venue: Puccini Dec. 8, 2016: Editors' Pre-regional Meetup Venue: Draft, Farmacy '''Dec. 9-11, 2016: Second SEA Regional Meetup <br />''' Venue: Makati Shangri-la, Philippines''' == 2017 == Feb. 5, 2017: Meetup for all Wazers <br /> Venue: Puccini March 24, 2017: Editors' Dinner <br /> Venue: Tori Ichi, Slice, and Shangri-la at the Fort March 30, 2017: Editors' Dinner and Drinks <br /> Venue: Ooma BHS; Craft at the Fort Strip April 15, 2017: Holy Week at Ayala at the 30th<br /> Venue: Tori Ichi '''June 30 - July 2, 2017: SEA Regional Beta Meetup '''<br /> Venue: Grande Centre Point Ploenchit, Thailand '''Sep. 2, 2017: Second National Meetup <br />''' Venue: Conrad Manila, Philippines '''December 1 - 2, 2017: Waze APAC Regional Meetup 2017 '''<br /> Venue: Pullman Bangkok King Power, Thailand == 2018 == '''April 13 - 15, 2018: Waze APAC Mega Regional Meetup <br />''' Venue: ParkRoyal on Pickering, Singapore May 27, 2018: Southies Meetup <br /> Venue: Bawai’s Vietnamese Kitchen, Nuvali '''Aug. 18, 2018: Third National Meetup <br />''' Venue: Crowne Plaza Manila, Philippines '''October 12 - 14, 2018: BetaLization Meetup <br />''' Venue: Courtyard by Marriott Berlin City Center, Germany == 2019 == February 3, 2019: Waze Cafe Venue: UP Diliman '''April 12 - 14, 2019: Waze APAC Mega Regional Meetup <br />''' Venue: Pullman Bangkok King Power, Thailand April 19, 2019: Holy Week at BGC <br /> Venue: Pink's Hot Dogs May 25, 2019: Waze Cafe <br /> Venue: Spiral June 8, 2019: Mapraid <br /> Venue: Google Office, BGC == 2022 == '''November 19, 2022: APAC Mini Regional Meetup <br />''' Venue: Sheraton Manila, Philippines == 2023 == '''March 17 - 19, 2023: Waze APAC Mega Regional Meetup <br />''' Venue: Bangkok Marriott Marquis Queen’s Park, Thailand 7572b90e1fb6078011c84369f2a2eee3bd28a262 0 3 10536 10405 2019-07-20T06:41:32Z Rccoros 5 /* Philippines MapRaid History */ wikitext text/x-wiki == Philippines MapRaid History == The Philippines was involved with the initial testing of the Waze MapRaid effort, although at first we called it Map Sweep. The community first heard about the concept during the official Philippines Waze Meetup conducted June 2014. The first Philippine MapRaid was held in September 2014, with the raiders arranged into three teams, tackling problems in Metro Manila. Subsequent raids were then held in various provinces/cities throughout the country. The community has since been using MapRaids to improve community involvement, to discover new editing talent, and to train new editors by putting high-level editors in charge of running the teams and mentoring lower-level team members. Many editors have achieved level upgrade because of their performance in the MapRaids. Visit the [[global:MapRaid|MapRaid]] wiki for more details. Here are some of the stats from the MapRaids that were done in the Philippines {| class="wikitable sortable" |- ! Date !! Location !! # of Raiders !! Segments Handled !! Segments Created !! MPs Resolved !! URs Resolved !! PUs Handled !! Previous Connectivity !! New Connectivity !! Change |- | Sept 2014 || Metro Manila || 10 || 3104 || 877 || 8 || 255 || 577 || 88.74% || 95.213% || 6.473% |- | Oct 2014 || Central Luzon || 14 || 136619 || 46810 || 772 || 3290 || 9529 || || || |- | Nov 2014 || Cavite and Laguna || 14 || 25702 || 8492 || 35 || 209 || 4200 || || || |- | Feb 2015 || Metro Manila || 16 || 26930 || 5396 || 0 || 3070 || 6411 || 93.6% || 95.5% || 1.9% |- | Dec 2015 || Metro CDO || 8 || 21324 || 8466 || 0 || 54 || 476 || 93.28% || 96.8% || 3.52% |- | Dec 2015 || Metro Cebu || 9 || 19653 || 6914 || 0 || 190 || 4363 || 97.72% || 98.4% || 0.68% |- | Dec 2015 || Metro Davao || 9 || 55917 || 23835 || 0 || 58 || 1921 || 96.94% || 97.7% || 0.76% |- |April 2016 || NCR || 22 || 41400 || 4100 || 0 || 2500 || 24700 || 94% || 95.3% || 1.3% |- |June 2019 || NCR and Central Luzon || 10 || 2809 || 562 || 0 || 383 || 2365 || || || |} [[Category:Philippines]] f499c318957a23e39dc08ff997264d820381eb75 1 20 10541 2020-09-23T11:17:11Z Nspascua 86 Created page with "someone created different pinned locations for our business to confuse buyers. please help us edit. pls. what do i do to delete or report other locations" wikitext text/x-wiki someone created different pinned locations for our business to confuse buyers. please help us edit. pls. what do i do to delete or report other locations f2896c6d699260595edc0a72269103919489037e 14 21 10544 2022-11-30T12:58:11Z Automatic category creator 111 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Philippines" as well as all subcategories of category "Philippines" if any exist. 750d9a3fd9acbaf35658da1cf20b8655ac5922d3 8 22 10545 2022-12-01T17:29:32Z Maintenance script 112 wikitext text/x-wiki File uploads are disabled for all the local community wikis. Please upload your files to the [https://wazeopedia.waze.com/wiki/Commons/Special:Upload main file repository]. 90bfeb8c0119d2ff36f07a275fa0747573e22538